Database Users

n1 broke

i rooted my phone but i forgot to perform a nandroid backup, so now my phone only turns on when i load a custom rom , does anyone know how i can get my stock rom back?????????

there is a tut of getting back to stock in the development section. or look on modaco.
your phone is not broken

dynomyar said:
i rooted my phone but i forgot to perform a nandroid backup, so now my phone only turns on when i load a custom rom , does anyone know how i can get my stock rom back?????????
Click to expand...
Click to collapse
You can search.

Well now that you've unlocked the bootloader there really is no point in going back to a stock rom. Might was well flash Cyanogen on it.

**Rooted Phones*** Reset back to First Time Root

Ok apparently in my futile attempts to OC the Pure Hero 1.0 Rom I've totaly got something hosed up. The phone works but features that others have working flake out on me. Is there a way to wipe fully the whole thing and reset back to the rooted 2.1 Rom as we did before the Recovery image.
If it is as simple as just flashing the original developers Rom please don't flame me..I did search.
I do a factory wipe then Dalvik Wipe then Ext Partition wipe before flashing an image.
I currently can't get Wifi to work on Punk.Kaos Rom nor on the Pure Hero (I think that was an issues though)..
Thanks for all the hard work you guys do....

copy a rom you want to use to your sdcard. then go into recovery, wipe the phone, then flash zip from sdcard. done!

That is what I have been doing and some of the settings are still flaking out and the Kaos rom is V15 he fixed wifi in v2. I can't even get Jamezelle's sensable rom to even flash with out a boot loop at animation.
Thanks for the help.

No nandroid backup?? I know before flashing the first Rom on the phone I made a nandroid back up on my wifes and pretty much do everytime before flashing a new rom. These things are priceless

Follow the the original root procedure.

*Suggestion*, when phone boots.... open setcpu and adjust the CPU OC setting.... maybe...

id say go to the downgrade to 1.5 from 2.1 root thread and do that and then re upgrade and reinstall the recovery image.

I agree with doing a full downgrade to 1.5 and rooting again. I had problems similar to yours and this solved the problem. Good luck.
-------------------------------------
Sent via the XDA Tapatalk App

Thanks I just wanted to confirm that should be the process of going to 1.5 thne to 2.1 and restoring the Recovery. One last question and then a Mod can close this thread. The Rom Manager in the Market will that work for us or is that a Droid only thing?
Thanks for the great advice.
Forgot to answer the nandroid backup yes did it before every new flash of a Rom they would come back weird also. Secondly how do I get my SD card back to full Fat32 and not the ext+Fat partition for A2SD mode? I never could get the A2SD to work fully.

flashing prep questions

Ok, so I'm currently using bionix 1.9 with stock kernel. I really want to flash bionix fusion with kingxklicks kernel, from what here this is a great rom.
My question, is there anything I should know about flashing this i.e. going back to stock rom? Is there anything I need to do before flashing this?
If I decide to go back to stock rom can I just flash with odin? Do I have to flash stock kernel before flashing back to a stock rom?
Can anyone just let me know, I would like to be prepared in case anything does go wrong.

Nope, you should be safe to flash directly over your current rom. As a precaution, if you have Ryanza's OCLF, you might consider undoing the lag fix... not saying it is needed but more often than not, most people who have a problem start off with saying " Help, I just tried flashing (xyz rom) and now I am stuck at the bootscreen. I had (abc rom) and OCLF before... what could be wrong?" Any other questions be sure to consult the red text in my sig.

Ok cool, even then I have been stuck on the boot screen a couple of time. Odin fixed that problem.
Sent from my SGH-T959 using XDA App

Other than making a nandroid backup and maybe a titanium backup, you should be good to go ...
Fusion 1.1 is a wipe ROM so may want to backup your apps ....

Questions about flashing roms

Hi everyone. I had a few questions about flashing new roms on my kindle and was hoping to get some help
1. If I flash a new rom, like cm7, will i need to use titanium back up to save my apps and data. I remember doing this when i flashed a rom for my phone.
2. will flashing to cm7 prevent me from receiving OTA updates that amazon sends out. They just recently sent one a few days ago and the update unrooted the kindle. I wanted to see if I this is something I would have to worry about if i flash to cm7
3. once i do flash to cm7 and say another rom comes out, can i flash straight to the new rom or do i need to flash back to stock then perform the flash for the new rom.. again i remember having to do this when i was changing roms with my phone.
4. does the battery need to be fully charged before flashing
5. If i flash to cm7 then want to go back to back up (amazon stock software with root and gapps) will this make me loose my root access and twrp 2.0
Thanks

babbabooey97 said:
Hi everyone. I had a few questions about flashing new roms on my kindle and was hoping to get some help
1. If I flash a new rom, like cm7, will i need to use titanium back up to save my apps and data. I remember doing this when i flashed a rom for my phone.
2. will flashing to cm7 prevent me from receiving OTA updates that amazon sends out. They just recently sent one a few days ago and the update unrooted the kindle. I wanted to see if I this is something I would have to worry about if i flash to cm7
3. once i do flash to cm7 and say another rom comes out, can i flash straight to the new rom or do i need to flash back to stock then perform the flash for the new rom.. again i remember having to do this when i was changing roms with my phone.
4. does the battery need to be fully charged before flashing
5. If i flash to cm7 then want to go back to back up (amazon stock software with root and gapps) will this make me loose my root access and twrp 2.0
Thanks
Click to expand...
Click to collapse
1. If you are coming from another rom, then yes. But if you are updating your CM7, then you should probably backup your apps
2. I have had CM7 on my Kindle for like 2 weeks, and have not received an update. So I don't think so.
3. Like I said above in number 1. For example: If you are coming from Cm7 and want to try to flash ICS, then you would first backup your system, then wipe system, data, cache and Dalvik-cache, just to make sure. But if whistlestop releases a new version of Cm7 that fixes the MAC adress, then you would boot into recovery, A backup is optional but is recommended., then wipe cache and Dalvik-cache only, then flash the updated rom on top of it.
4. It says that it is recommended to have a full battery, but I have not yet flashed a rom with a full battery, and I have not occured problems.
5. I think if you get an OTA update after flashing back to stock, then you will probably loose root access again and TWRP. But don't worry, after you get TWRP back, you will still have all your backups.

AWESOME! Thanks for all your help.
one more for you. so i just rooted and installed twrp and did a system back up. then i want to flash cm7. now i am running cm7 and decide to try ics so i do another back up before i flash to ics, will the cm7 override the original back up that i did before flashing cm7 or will i now have 2 different back ups i can restore if i wanted too.

babbabooey97 said:
AWESOME! Thanks for all your help.
one more for you. so i just rooted and installed twrp and did a system back up. then i want to flash cm7. now i am running cm7 and decide to try ics so i do another back up before i flash to ics, will the cm7 override the original back up that i did before flashing cm7 or will i now have 2 different back ups i can restore if i wanted too.
Click to expand...
Click to collapse
There will be 2 different choices when you go to restore. But the problem is that when you make 2 backups the same day, its hard to tell which is which. So when I make a backup I mount USB with the option and rename the 12-27-11... file to something like CM7-12-27 or something of the sort.
Sent from my LG-VM670 using Tapatalk

Thank you sir

[Q] safestrap / romslot 1 / issues

running stock rom on stock rom slot everything works fine, when i install a custom rom to rom slot 1 and boot to custom rom the rom works and does everything it should but i am not able to reboot or power off my phone. it does this if i am on custom rom or stock rom. when rebooting or powering off it gets stuck right after logo of rom goes away and stays there with led light, back arrow and open apps keys lit up. i have to remove battery and boot that way. after i wipe/ delete custom rom from rom slot 1 and everything works fine ??????

Dpike698 said:
running stock rom on stock rom slot everything works fine, when i install a custom rom to rom slot 1 and boot to custom rom the rom works and does everything it should but i am not able to reboot or power off my phone. it does this if i am on custom rom or stock rom. when rebooting or powering off it gets stuck right after logo of rom goes away and stays there with led light, back arrow and open apps keys lit up. i have to remove battery and boot that way. after i wipe/ delete custom rom from rom slot 1 and everything works fine ??????
Click to expand...
Click to collapse
If you would have read numerous threads on the issue you would have known. Instead you found out the same way I did some weeks ago!! There are known bug issues with Safestrap that cause the problems you are experiencing when using a rom slot. Use the stock slot only and all will work well. Yes, this means you have to wipe out your stock S5 system, but you can always odin back to stock.

Chopstix9 said:
If you would have read numerous threads on the issue you would have known. Instead you found out the same way I did some weeks ago!! There are known bug issues with Safestrap that cause the problems you are experiencing when using a rom slot. Use the stock slot only and all will work well. Yes, this means you have to wipe out your stock S5 system, but you can always odin back to stock.
Click to expand...
Click to collapse
With our build you pretty much have to treat safestrap like any other custom recovery. Most other recoveries that I'm aware of don't have various slots for you to dual boot stock and custom roms. Making a backup within safestrap is definitely recommended before you wipe the stock rom slot that way if you want to go back, you won't need to recover with odin. Not saying that's a bad way to go, just a little inconvenient.
Sad to say the developer of our recovery if off doing other things. I don't know if this rom slot one issue is something that can be patched within the recovery, or it's it's more of a ROM developer kind of thing, but I don't see that getting fixed any time soon.

DJNads said:
With our build you pretty much have to treat safestrap like any other custom recovery. Most other recoveries that I'm aware of don't have various slots for you to dual boot stock and custom roms. Making a backup within safestrap is definitely recommended before you wipe the stock rom slot that way if you want to go back, you won't need to recover with odin. Not saying that's a bad way to go, just a little inconvenient.
Sad to say the developer of our recovery if off doing other things. I don't know if this rom slot one issue is something that can be patched within the recovery, or it's it's more of a ROM developer kind of thing, but I don't see that getting fixed any time soon.
Click to expand...
Click to collapse
No it won't... Hash said in the safestrap thread that he was shutting down deveopment work on it... the only hope would be that another dev dives in to it.

Chopstix9 said:
No it won't... Hash said in the safestrap thread that he was shutting down deveopment work on it... the only hope would be that another dev dives in to it.
Click to expand...
Click to collapse
Considering it's open source, I'm hoping it won't be too long before another developer picks it up. (PlayfulGod maybe? )