Related
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
I think I found out the cause of some bootloopings and its the "Log Switch" option in project menu.
When we try to root the rom and the the phone reboots:
A)if he reboots ok, you must go again into project menu (*#*#2846579#*#*) and "switch off" the Log.
Everyone tell us we must switch this thing on in order to root the phone but no one says that we should turn it off again after proccess completed....
B) if starts immediatly with bootlooping and never booted againd after the rooting proccess just take the battery out andenter into recovery (vol up + Power). Once there make a "Data factory reset" and reboot.
The phone will then start normally this time with no Bootloopings.
With luck you have SU installed and the phone is rooted.
If yes, just go to project menu (*#*#2846579#*#*) and "switch off" the Log.
If not just try the rooting again
But the major deal is the Log Switch.
Hope it helps anyone
I never had bootloops with 2.3 official rooted and log switch was turned on before and after
I'm happy for you!
Moved to General
Thought this may be helpful to some, it has no place in the development section.
Thanks for the contribution, i would usually close, but as it could be helpful, on this occasion i will move it.
Take it easy
O_G
yes don't close it please as I noticed that many had bootloop issues with these releases. I was one of them but this finished after switching the log of. In my caes that solved my problems.
I had thought that too but none of the combinations i tried worked.
I had tried switching off Logging,factory data reset,flashed again without rooting and after 2-3 days that everything seemed that worked normal and i had loaded all apps i wanted, bootloop appeared again and had to factory data reset again in order to use phone.
So i gave up and reverted to 2.2
I never had bootloops but if that's really what's causing it, that's a great catch!
Congrats!
well as I said with me, since I have done this the bootlooping stoped.
Before Everytime I reboot the bootlooping started and only stoped with a factory reset. Then I tried to switch Log Off again and not a single bootloop and more than 48 hours.
Flashed OC kernel, UOT Kitchen, etc etc and phone running perfect.
Look, I have flashed and tested this rom many many many times and alwas endup with bootlooping eventually. This did the trick for me and I consider it a major step as I can now use the rom freely and without being afraid.
As I said, is just 1 more Idea that people having this issue could try out and see if helps.
I just took the liberty of sharing this so that in case o dispair for some, they can have other alternatives.
Didn't help me, actually it did the opposite...my phone didn't boot loop until I went and touched the freaking "Log switch" option...should have let it ON...GRRRR....Got to taste Huawei's bad medicine again...or my own...I should have known; if it ain't broken, don't try to fix it!
lololol
Huawei's each one with own personality...
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Tell me about it.
SilveRRing said:
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Click to expand...
Click to collapse
You understand it opposite m8.
You must turn the Lon On to root the phone.
After root my advice is to turn it back Off again as it was from the beginning..
Ah ok, nevermind then. lol
my x5 dont have bootloop but this topic will help very people,thanks for the trick lol
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
driuda you have a theme of UOT Kitchen??? I make one for me but failed,please help me?i dislike stock theme is for children hehehe
at the moment I only used UOT this time to change the battery icon to battery percentage circular.
Its one of those must haves that I miss from official rom, the battery percentage....
Coking a theme is very easy. You just choose all the option you want and in the end upload the framework-res.apk and SystemUI.apk files and wait for the coking.
After that pick up the file and flash it with CWM.
mhh i dont think that the log switch is the only thing that causes bootloops.
first i installed 2.3.5 and a few hours later i switched the og on. The bootloops started.
So i had to do a factory reset...
Now after the reset I quikly turned off the log switch. but just a few hours later it started again bootlooping......
any other ideas? or do i have to go back to miui? when yes can i do the following?
: 1. factory reset
2. get root
3. install cwm
4. install my backup?
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Druida69 said:
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Click to expand...
Click to collapse
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
levibuko said:
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
Click to expand...
Click to collapse
if it is to downgrade and then move forward to any other rom, custom or not, you can use any version don't loock spexifically to a german one.
Here you have a list of stock rom:
http://forum.xda-developers.com/showthread.php?t=1167882
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800 (MOdaco Wiki)
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8800_IDEOS_X5 (XDA Wiki)
Hi everyone. .
What's the easiest way to go back to an OEM ROM? I rooted my S4 and flashed several different ROMs ( which were awesome) but none let me encrypt my phone. I need to encrypt it so that I can access my work email. Ive decided to try and go back to stock and just root the stock ROM so I can delete all the sprint bloat and just be happy for now. Any thought on the easiest way to accomplish this? Im using TWRP recivery
Appreciate all the help!
R
rvv2002 said:
Hi everyone. .
What's the easiest way to go back to an OEM ROM? I rooted my S4 and flashed several different ROMs ( which were awesome) but none let me encrypt my phone. I need to encrypt it so that I can access my work email. Ive decided to try and go back to stock and just root the stock ROM so I can delete all the sprint bloat and just be happy for now. Any thought on the easiest way to accomplish this? Im using TWRP recivery
Appreciate all the help!
R
Click to expand...
Click to collapse
Everything you need is in this post: http://forum.xda-developers.com/showthread.php?t=2277480
Have you tried just flashing the stock rooted MDL rom from recovery? This is the fastest way to go back to stock rooted. The link to crawrj's stock rooted MDL rom is in that post as well. If that doesn't do it for some reason (not sure why it wouldn't) about your only choice then is to Odin back to stock.
Boom. Worked perfectly. I just flashed stock rooted MDL rom from recovery and rebooted a couple of times and it let me encrypt! I don't know why the first time I flashed it, it wouldn't let me encrypt. Weird.
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"
omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on
another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/
Hi everyone!
I am having very strange problem with stock rom "JORDN _U3_6.36.0" from T-Mobile USA on standard Defy. Each time i power phone up, it starts booting up then restarts itself in to stock recovery and perform hard/factory reset. After that it boots normally, but all settings gone.
I am not using T-mobile sim or moto blur account , so i skip registration using "ebluroff" trick. Is that can be the cause of the problem?
Some backstory: when i bought the phone it had CyanogenMod 7 installed on it. I used it for 2-3 years,even updated it several times up to 7.2.
Then some time ago i started having issues with it, so i had to flash stock rom with 2.1 Android.
I decided not to do anything with the phone, until i got some advice, so i any help would be greatly appreciated.
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
thekguy said:
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
DEN383 said:
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
Click to expand...
Click to collapse
Some update. After hours of digging i found out these thread http://forum.xda-developers.com/showthread.php?t=899450
So, i first flashed defy 2.2_boot_only FIXED FSB, then after reboot custom recovery started working, so restored Droid22 rom from it.
Phew, i knew it was possible. So now i have rooted chines (?) android 2.2.1 on my phone and working custom recovery. I am gona stick on it for a while until i find best 2.3.3. nandroid ROM.
Just wanted to clarify was it right order - first flashing fixed SBF then restoring nandroid backup? I couldnt get custom recovery working without updating bootmenu first.
I also wanted to add that i did custom recovery data|cash wipe before flashing fixed SBF, before AND after restoring nandroid backup.
I saw that lots of people had problem like me , hope my message will help.
Here is link to another forum which has working download links http://www.addictivetips.com/mobile...ed-rooted-android-2-2-froyo-on-motorola-defy/