Database Develop

Help on Entering Recovery and Flashing Please?

Okay .... I have sucessfully rooted the wife's original Verizon Moto Droid and I have installed CWM via ROM Manager. I have performed a backup of her current ROM.
From the looks of things here, I will just load the ROM I want to flash onto her sd card and then flash it via ROM Manager. Is this correct? If it fails half way through the flash, can I still enter CWM via the key sequence to re-flash/restore the phone to its original state using the backup on the card from ROM Manager?
I gave her this phone when I bought my Samsung Droid Charge when it came out back last March. I can flash ROMs & Kernels on that phone all day long but the Moto Droid is an entirely different animal. I want to be sure of my fail-safes before I flash anything here.
Thanx In Advance for Your Help

Okay ... cwm just didn't take the first time I flashed it. I am now able to enter CWM from a powered off state.
[Q] If I flash a rom and it doesn't take half way through the flash, will I still be able to enter cwm and install the backup of her current rom? That ROM is not in a zip format on the sd card. It is a tar file and the other components in a folder.
I want to be sure I can recover the phone if I experience a bad flash before I attempt anything. Remember, this is my WIFE'S phone !!! LOL
Any help appreciated.
Edit: Also, I installed RSD lite on my computer but when I open it and hook the phone up, it doesn't see the phone. At least, from what I can tell it doesn't. I click 'show' device and nothing happens. Is this a flashing tool or do I put the ROM on sd card and flash via rom manager? And the fail-safe !! Gotta have the fail-safe !!!

Tips on Flashing Kit Kat Update

I want to manually flash the Kit Kat update by downloading it the zip file and installing it through TWRP. I'm fairly new to the Android customization side, but I have caught up pretty easily knowledge-wise. My device is rooted with Scott's Cool Rom and Faux123 Kernel installed which I plan on removing and going back to Stock because I keep getting random restarts for no apparent reason while using my Nexus. Before I start the process of flashing 4.4, I need some advice from the community to reassure that I am going about my objective the right way.
List of Steps
1) I will create a nandroid backup of my device (just in case something goes wrong).
2) I will do a factory reset (wiping data, cache, and dalvik only) to remove Scott’s Rom. This should also remove root.
3) I will then set my device to developer mode.
4) I will copy 4.4 update to my SD.
5) I will log into recovery mode and flash install the update from there.
If there is anything I am missing, please let me know. Also if you have a recommendation for rom or kernels I can try please let me know. I'm thinking about flashing the USB Rom that enables charge while using other USB devices thru OTG simultaneously.
Any helpful advice is welcomed and encouraged.
Thanks in advance.

I dont think many can visualize what you are trying to do starting from step 2...
See, you cant remove a rom without wiping system.
Yet after removing rom you wanna go boot up android and enter developer mode? What rom will be left?
Maybe what u meant was resetting rom?
Basically to return to stock or flash a stock image, this is a well known method as it's a complete clean flash:
http://forum.xda-developers.com/showthread.php?t=1907796
1.If you dont have the intention of deleting your rom(dirty flash), then you can just execute steps 1,2,4,5.
2.If you have the intention of removing your current rom(clean flash), you have to follow the link above.
Also, is your USB ROM timur's usb rom? Afaik the latest release of that is 4.2.2 base...
For 4.4 i'd recommend Purity rom + franco r76 as of today. I dont think it has usb host charging mode tho. Good luck!

[Q] xperia z stuck at boot screen

Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?

druvisk said:
Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?
Click to expand...
Click to collapse
hey if you wana go back to stock rom follow this post forum.xda-developers.com/showthread.php?t=2240614
i think u have to fastboot and flash boot.img
try pacman rom which is better and bug free rom

Hi, are you still able to connect to flashtool in flashmode? If so have you tried to flash back to stock rom?
Check this thread out, it contains good stuff.... 3rd video show how to flash stock ....
http://forum.xda-developers.com/showthread.php?t=2275632
Good luck !!

Hello,
thx for your replies i m still able to access all the modes it just does not load up if i dont do anything
after i unlock the bootloader to i need to reroot the phone ?
as it seems right now to me it simply doesnt write anything when i try to flash the rom also some partitions are not available

Hello,
i managed to unbrick the phone using this tutorial http://forum.xda-developers.com/showthread.php?t=2458530
however i tried to redo all the steps following the guide to install the beanstalk rom and noticed that i m getting an error about updater package when i try to execute the installation from TWRP any ideas ?
would you suggest trying another 4.4 based rom ?

Hello again,
ok so i gave up on the beanstalk 4.4 rom and decided to try my luck with pac rom mtayabkk suggested
so now the problem is not as big as it was.
Able to get the rom to run however i m unable to import my contacts/sms/call log using titan backup
The restore seems to work but after that i m getting com.android phone has stopped error everywhere i go on my phone (the contacts/etc are actually restored in this process tho and work fine apart from the errors)
i did restore a bunch of other settings together with the contacts aswell which i found as safe to back up in a guide i found
so can you give me an advice how to properly restore this to the newest pac man rom and avoiding various errors after that ?
ps
i moved all my media to sd card so it does not concern me the only thing i cant seem to be able to move over apart from contacts/sms/call log are the APN settings which is bothering me a bit aswell as i can not receive the configuration messages from carrier but i found them on the internet and i will add them manually
trying to restore the stock backup from PC companion right now to export them again as i lost the backup in process of trying to deal with the error i was getting
would you suggest trying again with titan backup or any other tools ?

[Q] Help - N7000 - can't flash new rom - getting EMMC message

Hello All,
I've spent the last 6 months learning how to flash roms, realise you need the right kernel and made many mistakes which resulted in bricking my phone. I've learnt a lot and as you often suggest on this site, read and learn. I've been trying my best to do this over the months and have managed to even use Odin, after about 70 hours reading, track down a kernel XXLT to get my phone back into recovery and many other painful experiences.
I thought i had the basics down pat by now but i've bricked my phone this time and I'm truly stumped as it brings up an EMMC message and nothing i do with Odin or flashing kernels afterwards brings the phone back at all. I'm sure it's on here somewhere and you will point it out to me but I have tried as it's the only way to learn. Now, if you are willing, i could really benefit from some expert advice?
I have been running CM11 for the last week, really enjoying how it worked on my n7000. I was doing some further reading and came across the page for the Forest Kernel for CM11 on the n7000. I thought no problem, download file, follow flash instructions (wipe dalvik) and proceed as normal. But the zip file would not load and the recovery aborted. I was using CWM touch and in the malaise that followed, i now can't rememer which one it was but it was the grey screen one with the touch functionality.
I thought maybe i didn't have the right CWM to flash this file so I thought I would try a later version of CWM but use PHilz' touch version - using the 'about in recovery' it has v 6.0.3.7.
So i flashed the file again using Philz' version and then i just got a lot of fast scrolling text and I was stuck in recovery from that point on. I tried wiping for reinstall , installing raw kernels and everything i think i know about trying to fix it myself.
However, with lots of fast scrolling text going by, i started looking more closely at it and noticed this message:
Created filesytem with 11/32768 inodes and 4206/131072 blocks
warning wipe_block_device: wipe via secure discard suppressed due to bug in emmc.
now flash a new rom
Since this message, nothing works from the flashing a new ROM in recovery onwards. I just get message like cannot load .ini or failed to open zip etc.
Now i did spend time months ago reading about teh ICS emmc recovery problem but because I've been on 4.4.3 to begin with i thought I'd already surpassed the problem.
I've been running Slimsaber and recently CM11 on KK 4.4.4 so i didn't think i could initiate an 'emmc' problem.
So now i'm stuck and of course, bricked my phone just when i need it most. I only undertook flashing the Forest kernel because it seemed such a low level risk, wipe dalvik and flash.
If any of you could offer some advice, yes, even if you tell me to read it etc, I will understand. It's just after having taught myself so much from these pages I seem to have met my match this time in recovering my phone, so any advice or assistance will be appreciated.
I understand though if asking for this help is inappropriate.
Thanks in advance.
Regards,
Paul

For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...

Did you try to flash a stock Samsung JB rom using Odin and start fresh?

I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.

ThaiDai said:
For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...
Click to expand...
Click to collapse
Dear ThaiDai,
Sorry, when it goes wrong, it certainly is chaotic. The whole process of going wrong snowballs.
I'll try and follow your advice, thanks for your help.
Cheers,

nokiamodeln91 said:
Did you try to flash a stock Samsung JB rom using Odin and start fresh?
Click to expand...
Click to collapse
Hello Nokiamodel. Thanks for your help. No, i didn't. As i ended up stuck in Philz touch recovery, I tried pushing a raw kernel on via Odin.
When i bought this phone, it came with Gingerbread on it so does that mean i should use gingerbread to return to stock?
cheers,
p

majaretilla said:
I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.
Click to expand...
Click to collapse
Majaretilla, thanks for this advice.
I was about to do this when i remembered reading somewhere on another forum that sometimes taking the battery out can sort something like this out. I took out the battery, and when i put it back in, it did not boot into philz touch recovery but what i now realise is the stock recovery. It's the one where you move the cursor by using power and volume keys.
This recovery flashed over the kernel and then roms I had onboard the phone until i got it back to CM11.
The only thing I can't crack now is why that Forest CM11 kernel won't flash using CWM or Philz. It gets aborted. I've tried v2, v4 and v5 and it never works.
I can't find out why or how to overcome the problem so I think i'll leave well alone. It's justfrustrating not knowing why it doesn't.
Thanks again for your help,
p

[Q] ROM flash gone wrong. HTC one M7

Hi,
Looking for some help from you guys if possible. I have have been flashing Android HD Roms by Mike1986 for some time now on my HTC One (M7). Last updated to HD-One_91.1 to upgrade to Lollipop. Experienced very poor battery performance so looked to flash back to an earlier Kitkat version. Instead of flashing a previous one, I thought i'd give the Google 6.1_GE a go and see what that was like.
Big problems. Phone kept getting stuck in boot loop - so eventually i decided to wipe the phone and start again. Now when I switch phone on It boots into the start screen for Goggle edition then reboots constantly.
As I wiped the patition, I do not have the option to reinstall even the Lolipop ROM.
My phone wont stay on long enough to copy another ROm over. so Im stuck with a pjone that keeps switiching off before I can do anything with it.
I use TWRP recovery but when i try Factory reset etc, same problem occurs.
How can I get another compatible ROM onto the phone or am I stuck with a knackered phone?
Any advice greatly appreciated.
Thanks in anticipation.
DrG.

DrGunlove said:
Hi,
Looking for some help from you guys if possible. I have have been flashing Android HD Roms by Mike1986 for some time now on my HTC One (M7). Last updated to HD-One_91.1 to upgrade to Lollipop. Experienced very poor battery performance so looked to flash back to an earlier Kitkat version. Instead of flashing a previous one, I thought i'd give the Google 6.1_GE a go and see what that was like.
Big problems. Phone kept getting stuck in boot loop - so eventually i decided to wipe the phone and start again. Now when I switch phone on It boots into the start screen for Goggle edition then reboots constantly.
As I wiped the patition, I do not have the option to reinstall even the Lolipop ROM.
My phone wont stay on long enough to copy another ROm over. so Im stuck with a pjone that keeps switiching off before I can do anything with it.
I use TWRP recovery but when i try Factory reset etc, same problem occurs.
How can I get another compatible ROM onto the phone or am I stuck with a knackered phone?
Any advice greatly appreciated.
Thanks in anticipation.
DrG.
Click to expand...
Click to collapse
Your phone must be s-off to use this rom like said in the OP. Also said that your phone WILL bootloop if you flash it without having s-off.
Android Revolution HD 6.1
Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
You can't use ART with deodexed custom ROM
You need TRWP 2.6.3.3 custom recovery!
--- MD5 Checksum: 2A9CD96A42C79D64A7933ECE76AD84E6 ---​
Click to expand...
Click to collapse
Boot in recovery (twrp), push a rom to your phone using adb push, adb sideload or MTP (MTP only available on newer twrp versions) and then flash the rom.

alray said:
Your phone must be s-off to use this rom like said in the OP. Also said that your phone WILL bootloop if you flash it without having s-off.
Boot in recovery (twrp), push a rom to your phone using adb push, adb sideload or MTP (MTP only available on newer twrp versions) and then flash the rom.
Click to expand...
Click to collapse
Ahhhh!!!! RTFp eh? Well thanks for that. I'll try again and hopefully Will be ok.
Thanks for taking the time to reply.
Cheers
DrG