Active Topics

 


Reply
Thread Tools
Posts: 290 | Thanked: 385 times | Joined on Jan 2012 @ Madrid, Spain
#21
Hi.
Does anyone know if this can help at least to make a backup?
http://manpages.ubuntu.com/manpages/.../0xFFFF.1.html
There's a "dump" option....
Regards.
 

The Following 3 Users Say Thank You to pasko For This Useful Post:
pichlo's Avatar
Posts: 6,445 | Thanked: 20,981 times | Joined on Sep 2012 @ UK
#22
The "Supported devices" section should be a giveaway.
 

The Following 5 Users Say Thank You to pichlo For This Useful Post:
Posts: 119 | Thanked: 217 times | Joined on Feb 2015 @ Poland
#23
How to make a RPL backup? USB cable and pirated soft is enoufg, or some special hardware is needed?
Could you give me examples of such soft and hw. (I'm scared I will break mine phone soon)
 

The Following 4 Users Say Thank You to badpixel For This Useful Post:
Posts: 119 | Thanked: 217 times | Joined on Feb 2015 @ Poland
#24
https://github.com/filippz/kernel-ad...1c54b344ffc9fd

n9: fix for CMT not working

CMT would fail with WAKLINES TEST FAILED error. The underlying cause
was usage of function irq_to_gpio that returned wrong GPIO number
for a given IRQ number (it returned 87 instead of 151 for cawake IRQ).
Subsequently ssi_wakein function would always inspected wrong GPIO pin
and always retuned "high" causing ssi_wake_tasklet to misbehave.
To avoid this ssi_resources array now contains GPIO number (not only
IRQ) and omap_ssi stores that GPIO number in omap_ssi_port struct as
wake_gpio alongside IRQ number (stored in wake_irq). This removes the
need for irq_to_gpio function.

Signed-off-by: Filip Matijević <filip.matijevic.pz@gmail.com>
Does this fix new-kernel-only bug, or also kernel-plus/defautl kernels are also affected by this bug?
 

The Following 4 Users Say Thank You to badpixel For This Useful Post:
filip.pz's Avatar
Posts: 108 | Thanked: 579 times | Joined on Feb 2013 @ Požega, Croatia
#25
Originally Posted by badpixel View Post
https://github.com/filippz/kernel-ad...1c54b344ffc9fd



Does this fix new-kernel-only bug, or also kernel-plus/defautl kernels are also affected by this bug?
This only fixes v3.5 kernel issue with CMT (ie working with older kernels and not with v3.5)

For conspiracy theory supporters: last official update for our N9 was "3G network compatibility fix"

For HW enthusiast: google for N9 Schematics and check how's CMT connected. According to schematics CMT is connected to OMAP3630 only, so there is no other way to access it if OMAP3630 is not able to communicate with it.

Since I've destroyed my N9 that had this issue (I have another with different CMT problem), can someone paste dmesg output? I guess there should be something that will tell us if OMAP can communicate with CMT and (in case it does) what's wrong.

I still have my money on HW issue.
 

The Following 13 Users Say Thank You to filip.pz For This Useful Post:
kick's Avatar
Posts: 82 | Thanked: 129 times | Joined on Jan 2017 @ India
#26
please continue here: http://talk.maemo.org/showthread.php?t=98857
i have a similar problem but i can boot into my n9 can you tell me what to do
 

The Following 2 Users Say Thank You to kick For This Useful Post:
Posts: 697 | Thanked: 1,980 times | Joined on Jun 2015 @ Lisbon - Portugal
#27
Found this and don't know if it helps
They talk about Factory BB5 RPL Writing Fixed

http://www.clangsm.com.br/topic/3828...nctions-added/
 

The Following 4 Users Say Thank You to deutch1976 For This Useful Post:
Posts: 1 | Thanked: 3 times | Joined on Jun 2017
#28
Hello Friends,

I got a nokia N9 from an online store last week. it came with Chinese Firmware. so i wasn't comfortable with it so i decided to flash it to another variant (Eurasia to be specific) using phoenix flasher. During the flashing it got to 80% then stopped with an error. Since then i couldn't connect to the PC anymore. Now, it starts up with a warning turned on that my phone is no more supported by nokia ....etc that i should reinstall the software that came with the phone. booting to desktop, my imei,network are all gone, showing SIM error. Now,the phone freezes with screen washing out until i restart it. it show "Phone connected in non-compatible mode"making it difficult to re-flash.

Please help me guys. i just used the phone for just a week.

thanks.
 

The Following 3 Users Say Thank You to reak For This Useful Post:
Posts: 803 | Thanked: 1,585 times | Joined on Aug 2014
#29
Have a look in this thread and see if it appertains to your situation:https://talk.maemo.org/showpost.php?...83&postcount=6
 

The Following 3 Users Say Thank You to aspergerguy For This Useful Post:
Posts: 20 | Thanked: 34 times | Joined on Oct 2018 @ Sweden
#30
I have the exact same issue.

The phone battery was drain (due to old phone, nothing unexpected.)
I start the flasher and having a hard time relocating the .bin image to a specific folder to get access to it from the flasher.

My intention was as u can understand to charge the drain battery with the flasher.

What I did not know was that the phone had charged during the time of
relocating that .bin file.
I start the flash sequence, and HOLY **** the battery is at 17%, the process keep going.
Try to stop it as fast as i can.
But no.

Now it seems it wont flash any firmware I try.
 

The Following User Says Thank You to Gamerouge For This Useful Post:
Reply

Tags
nokia n9

Thread Tools

 
Forum Jump


All times are GMT. The time now is 10:28.