EDIT: My phone is now working. Read at end of OP Below for the trick. Credit goes to thomascw: http://forum.xda-developers.com/showpost.php?p=21173699&postcount=69
My phone is going into a cycle that I am unable to get out of.
I followed instruction on how to fastboot flash recovery and update to whatever rom version.
My phone baseband is the 347 US stock rom. Here is the cycle my phone is getting into:
I have placed the update.pkg in the root of my sd card (At various times I tried various roms but always matched the region between recovery and rom)
I flash the recovery image using fastboot. Both my phone and my command prompt (I use linux) say OK and writing is done.
I do fastboot reboot and the phone reboots fine.
I hold the (vol+,vol-,pwr) keys to boot into recovery. When booted, it always show the correct recovery image that I just flashed. So seems OK!
I highlight the 2nd option which is the update from sd card. It goes fine and it finishes installation.
The phone boots but it gets stuck at the dell logo indefinitely. The phone is not responsive at this point and only removing battery is the option.
I replace the battery and let the phone boot but it shows me this message
Start emergency recovery copy....
Click to expand...
Click to collapse
Apparently the device is rewriting stock recovery into the recovery partition.
The phone reboots after finishing the copy into recovery mode again asking me to reset, update, ...etc.
This cycle always happen no matter what rom versions I choose. Well, stock roms only. I did not try modified ones.
I am unsure how to get out of the cycle as I tried every option, like reseting after flashing. I even flashed a backup copies of the 347 system and boot images. Always goes at the end to rewrite the stock recovery image (steps 7 and 8 above).
- SOLVED: last night, I flashed 360 as mentioned in steps 1-5 above. now, Instead of step 6 above, do these:
After streakmod recovery image flashed, fastboot reboot then vol+,vol-,pwr to go into recovery mode.
choose option 2 (upgrade from sd card) --- this will take you into another menu with more options.
Choose factory reset, wipe data, wipe cash,dalvik cash and all that.
Next get to advance option listed. From there, choose fix permissions (not sure if this is necessary but I did it anyway.)
From android back button, go back to previous menu.
Choose the reboot option.
Again hold vol+,vol-,pwr to go into recovery mode. Now choose factory reset (not sure if important, but did it anyways)
Phone will reboot into the rom you installed in step 5 above.
It worked from first time. I got encouraged and I even followed the steps again and I installed GB stock rom and also worked from first time. I am not sure I like the GB 407 rom over the 360 ROM, especially I get the annoying flashing lights every now and then because of the mismatch between the 407 region 14 and baseband region 00. But this is another issue.
Did you at some point try a Gingerbread based ROM? I have seen others have issues reverting to Froyo after that.
If you can get to recovery, for the ROM you want to run:
Make sure the pkg file for your ROM is on the root of your SD Card and is named update.pkg
Flash the amss.mbn file, dsp1.mbn file and the recovery.img with fastboot.
use the command fastboot reboot to reboot your Streak and make sure that you go directly to recovery
Now select step 2 and do the update
Since there is no pkg, recovery, amss or dsp1 files for BB 347 you will need to use a different baseband (I use 351, 360 is the latest). Use 407 if you must have Gingerbread.
ROM and related file Downloads
Flashing Guide
My take on Streak modding
Edit: the above steps should work even if you have never tried installing a Gingerbread ROM.
Thank you.
I've done all the steps you mentioned, except the second point. I never tried them. At least I have some new steps to follow. To which partition shall I flash the *.mbn files? Where do I find these files for a specific rom?
OK. Found amss and dsp1 files that are bundled with recoverySM.img (custom one), can I use these files with any ROM or are they rom and/or regional specific? I am confused because I do not see these files in the wiki page with the stock roms.
OK guy forgive my ignorance. I found the corresponfing .mbn files under manii's directory provided by your links.
I am trying them now. Crossing fingers and will let you know how it goes.
Thank you.
Back to the cycle. I added flashing both amss.mbn and dsp1.mbn to the process, but got the same pattern. I used the 360 build downloaded from mirror2.streakdroid.com/manii/360 directory. After the flash, the device hangs on dell logo screen. I remove the battery and replace it. I turn it on, and let it boot but this time it reverts to the emergency stock recovery image 347.
I will try tomorrow to get custom GB roms and see if they work.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
That's a well known issue with 347 firmware.
You should use streakflash tool to restore it to 305 lowlevel fw version, and continue from that point.
Very detailed article of using streakflash:
http://forums.whirlpool.net.au/archive/1557150
I'm experiencing exactly the same problem: I tried to update 347 to 360 and now I'm stuck at the boot logo :-(
I tried several stock images and yet no luck... Even the article mentioned above won't help me out ouf this misery.
Is there something else I could try?
ive also had this 4 or 5 times, so i replaced my inner sd with a 2gb sdhc ,think maybe the card was at fault
Dikos found an answer some where
Flash stock 360 recovery
Reboot
Hold Volume buttons
Option 2 - Recovery mode
Install stock 360 rom.
Fastboot
Flash streakmod
Hold Volume buttons
Option 2 - Recovery mode
wipe cache partitions and dalvik cache
Reboot
Hold Volume buttons
Option 1 - Factory Reset
Worked for me,now using 407 olleh, was on 360 for an hour,the key appears to be flashing back to streakmod and wipe cache partitions and dalvik cache before factory reset
I think this should be stickied
Well, whatever a "dalvik cache" is, it even works without clearing it!
Unfortunately my baseband is still at 347. Is that the reason for my leds to flash about 9 times every minute?
apirec, clear dalkic cache is under advanced options in steakmod recovery. The flashing is probably related to needing to flash the right amss and dsp1 mbn.
path to streakmod
Can anyone please confirm the link to latest streak mod.
Is it same as the link on
http://forum.xda-developers.com/showthread.php?t=840326 for
recovery-v0.3.2.8-beta.zip
-Mohan
thomascw said:
apirec, clear dalkic cache is under advanced options in steakmod recovery. The flashing is probably related to needing to flash the right amss and dsp1 mbn.
Click to expand...
Click to collapse
No, I did clear that cache, too (for the first time). But then I did the procedure again (without clearing that cache) to get the right baseband and to get rid of the flashy leds.
How would I flash the right amss and dsp1 mbn?
Mohan Nade said:
Can anyone please confirm the link to latest streak mod.
Is it same as the link on
http://forum.xda-developers.com/showthread.php?t=840326 for
recovery-v0.3.2.8-beta.zip
Click to expand...
Click to collapse
Yes, that's the correct link.
---------- Post added at 10:31 AM ---------- Previous post was at 10:02 AM ----------
apirec said:
How would I flash the right amss and dsp1 mbn?
Click to expand...
Click to collapse
Ok, found it myself: http://mirror2.streakdroid.com/manii/360/
But what are the other files for? Will it do any good, if I flash them, too?
If you have flashed recovery and gone through update, as far as I know,all you need are the amss and dsp1. I've read that the update.pkg reflashes the baseband, not true on my phone. One of the multirecoveryflasher tools has a baseband flasher built in. I havent used it, but it I think it probably just flashes the above 2 files.
thomascw said:
Dikos found an answer some where
Flash stock 360 recovery
Reboot
Hold Volume buttons
Option 2 - Recovery mode
Install stock 360 rom.
Fastboot
Flash streakmod
Hold Volume buttons
Option 2 - Recovery mode
wipe cache partitions and dalvik cache
Reboot
Hold Volume buttons
Option 1 - Factory Reset
Worked for me,now using 407 olleh, was on 360 for an hour,the key appears to be flashing back to streakmod and wipe cache partitions and dalvik cache before factory reset
I think this should be stickied
Click to expand...
Click to collapse
Thank you here again for pointing out the solution. I have updated my OP to reflect the solution to this problem.
Related
I downloaded my version of choice from the wiki but it is an "img" file.
Because of all the updating I've been doing, my phone only updates from zips now. How do I install the "img" file?
Thanks
Wait...
You downloaded an .img file? That means you downloaded the recovery image for the ROM you chose to use rather than the ROM itself. Stock ROMs use .pkg as an extension. In any event, you need to download the recovery image for the ROM version you choose to use anyway, because you will need to replace your existing recovery image with the one you downloaded in order to be able to flash a stock ROM.
I think I have this figured out. I have to flash the recovery img to my phone using fastboot then use the phone's recovery feature to install the pkg, correct?
Yup, that is correct
Make sure the update.pkg is on the root of your sdcard.
Make sure to backup before proceeding just in case.
I ended up back on simplestreak because nothing else would go back on and be stable, not even the nandroid I made a few days ago would run.
Put on the most basic version with no upgrades and it isn't too bad, although last night in the middle of a game of Angry Birds the screen went black and the phone restarted. Did it twice then started behaving properly again.
Might wanna try doing a factory reset after flashing the rom
If you still have StreakMod Recovery (the custom recovery) can also try wipe delvik cache and wipe cache partition then do your flashing
As usual, do a backup before proceeding!
Wipe all that before flashing? I keep doing it afterwards because that's what I saw for instructions somewhere.
mid_life_crisis said:
Wipe all that before flashing? I keep doing it afterwards because that's what I saw for instructions somewhere.
Click to expand...
Click to collapse
Oops ... mistype that ... your right, should be after.
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
omni_angel7 said:
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Click to expand...
Click to collapse
LOL, post usually note that the initial boot after flash is ridiculously long..... but I definitely waited >10 mins, almost an hour at longest on the Alien 3 beta flash just now, then I pulled batt and Fruit caked to 2.3.4.
(worried I might turn the soft-brick to a Hard-Brick if the battery died)
bamastang said:
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
Click to expand...
Click to collapse
Yup still have the unlocked text...... :-/ FRUSTRATING
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
defnow said:
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
Click to expand...
Click to collapse
lol, it seems like no-one who has had this problem has posted till now? xD
But did you finally get into the launcher? or a complete Boot animation???
do you using correct kernel?
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Jean-DrEaD said:
do you using correct kernel?
Click to expand...
Click to collapse
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Jonestown said:
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Click to expand...
Click to collapse
I used the pudding/fastboot oem unlock method for x64 windows, the application put together should do the exact same thing but without the user needing to do the actual steps individually, but any ways will give it a go
weaz_da_smel said:
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Click to expand...
Click to collapse
flash kernel after flash the rom because that... try FR an ATT kernels...
weaz_da_smel said:
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Click to expand...
Click to collapse
start from scratch...go back to stock via RSD...
DO NOT DO THIS
if the fuse is blown YOU WILL BRICK
I would fruitcake back to 1.83 then flash to the rom you want, since its voda I would try a working international rom first.
DO NOT GO BACK VIA RSD YOU MIGHT HARD BRICK.
wipe all data in fastboot -> flash stock 2.3.4 via fastboot -> wipe all data again
Not trying to hi-jack the thread but I have the exact same problem so I thought I'd post here and give a detailed description of what I've done instead of creating another thread just like this one.
I unlocked the bootloader using the latest version of pudding
Then I downloaded fastboot and installed CWM
I downloaded the ROM of my choice meaning Alien 3 and the theme, and later when that didn't work Redpill 3. Also for the record I've tried installing with Alien 3 standalone and wait for boot up, and with both - neither worked and Redpill produces the same result.
Anyway back to the process
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
The only way to get unstuck is to reflash with 183-sb-release.zip which is the fruitcake release I think. I got this from someone on a forum describing a similar problem for which this was the solution. However afterwards he was able to reinstall a custom rom without problems, while my problem remains.
*Edit - I have an AT&T phone
diviluxfloss said:
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
Click to expand...
Click to collapse
To double check -> Are you using latest unlocked CWM from xda or rom managers one?
Also to double check -> you did Wipe data / Factory reset as well?
You should do all three Wipe options before and after flashing the rom -> wipe cache, wipe data / factory reset, wipe davik.
After that reboot and give it a couple of minutes to boot.
If that doesn't work, do a battery pull and try booting again.
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
diviluxfloss said:
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
Click to expand...
Click to collapse
Alright, then the second thing I would try is flashing one of the custom ROMs via fastboot:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
p.s. and if you don't have the latest radio,-
moto-fastboot flash radio radio.img
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
diviluxfloss said:
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
Click to expand...
Click to collapse
The only truly dangerous method of flashing is SBF (RSDlite). CWM and fastboot are safe.
If you unlocked the bootloader youserlf, you already know what fastboot looks like. Often, fastboot helps where CWM fails.
Before using fastboot, make sure you have phone drivers installed, also make sure you have "moto-fastboot" version and not "fastboot", as the latter can't flash large files, e.g. - system.img.
Phone drivers for Windows x64 can be downloaded here (though your probably have them already if you unlocked the BL) -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Download moto-fastboot for your operating system here (if you don't have it already, obviously) -
http://forum.xda-developers.com/showthread.php?t=1138092
"Radio" is software that handles cellular connection, mobile data, etc.
I've read that there could be a boot problem if wrong radio is used.
Besides, the latest 2.3.4 radio includes many bug fixes and better mobile data speeds.
You can check if you have the latest one under "About Phone" -> "Baseband version". Latest one for ATT is N_01.77.30P.
It can be downloaded here - http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
(The archive contains all stock 2.3.4 partitions, but you can simply extract radio.img and flash it separately via fastboot)
Cheers.
Great
I'll try flashing the radio and then the files as mentioned in your previous post. A problem though is that when I look through the zip files I only find a boot.img file for the custom rom.
Where is the system.img file located and if I simply install these through moto-fastboot (thanks for the heads up btw as I only had fastboot) what happens to the smaller files located on the zip which won't be associated to the img files?
*Edit I compared these to the fruitcake zip and in the custom roms I have a folder called system which I believe contains all the info while the fruitcake files have an img. I'm guessing not compatible? Or can I simply make an img file with the system folder and flash thusly?
Hey guys. I just updated my Legend to the newest stable CM (with dalvik wipe, using ROM manager) and it freezes upon booting. I can get to recovery mode and I have ADB.
What do I do ? Is there a way to flash a ROM using ADB ?
It's been a long time since I worked with this stuff.
I don't think you can flash from ADB.
I suggest try to download the Cyanogen 7.1.0 rom again and check the MD5 after to make sure it is intact, I downloaded directly onto my phone then used ES file manager to check the MD5 # I had to download a few times because the MD5 # was not correct.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
grandioso said:
Hey guys. I just updated my Legend to the newest stable CM (with dalvik wipe, using ROM manager) and it freezes upon booting. I can get to recovery mode and I have ADB.
What do I do ? Is there a way to flash a ROM using ADB ?
It's been a long time since I worked with this stuff.
Click to expand...
Click to collapse
A quick question in your method, did you ONLY wipe the Davlik cache or did you wipe the system as well? I think you will have to wipe system & davlik when flashing a different rom.
How do I find out if md5 is correct or not ?
More importantly, what do I do after I donwload it ? It's not like I can do anything with the phone now, except get to recovery mode and control the phone via ADB in recovery mode.
And I only wiped dalvik cache.
I have help out someone with a similar issue here
http://forum.xda-developers.com/showpost.php?p=18597552&postcount=2
If you want to check MD5 # on the computer goto google and search for a MD5 file checker, ok you might want to know what MD5 is? its a check sum, the correct check sum is on the same page you downloaded on the cyanogen website.
if you know adb commands then you could always "push" the rom zip file to the sdcard on the phone, then flash it using CWM you'll need to wipe system and davlik at the very least.
First try to wipe data factory reset, wipe cache and wipe dalvikcache.
Reboot and it must be OK.
If it doesn't work download again cm7 stable, and flash it again with the 3 wipe.
I did a "clear storage" from HBOOT, but it didn't work.
When I get into recovery, I get a screen with a red exclamation mark. I guess that means I don't have CWM recovery. I have the files on my SD card, but htey have been copied from my previous one.
So I guess I'll need to flash CWM again...
You must have used fake flash to flash the rom correct?
Boot it into recovery and press the vol up button and the power button together ok?
It might give you an error once but press it again and again and you'll get into android recovery ok
Then go to install update.zip and cycle down to it using vol up and down buttons and the power button to select ok
Then it should load up clock work mod and you can use the trackpad now
Select mounts and storage and select mount SD card
Then connect USB and put the newly downloaded rom on your phone and once it's completed go back and go into advance settings I think... And do wipe cache and etc... Then go on install from SD and select your rom
Hope it helped
I flashed the ROM from ROM manager. I had CWM, but I don't anymore, because I changed SD cards. I have come to the point where I only need the goddamn update.zip file, but I can't find it anywhere and I think I'll go mad if I don't find it NOW
EDIT: Ok, I found it. At least I did a backup of my previous SD card....
I just did the biggest F-Up of my flashing life. While following QBKing77's Rooting & CWM with unlocked, at approx 3:50, during the flashing of the root SYSTEM.img file, rather than that file, I used the wrong file to flash used an IMG file that was meant for cwm, which is a completely different task.
So now I am trying to get into fast boot and try to do it with correct SYSTEM.IMG, then to find out I never got it downloaded, the link was deadand now I can not find where to DL it from. I must've not been paying attention and got ahead of myself.
Anyone know where I can a mirror of the file found here. Its the first link in the root section labelled "moto-fastboot flashable /system image".
Am I screwed? Does anybody have a copy of that system.img file laying around. I can not find any mirrors. That is the only way I can see this getting fixed bc I can still go into fastboot mode.
ckeck this ????
http://rootzwiki.com/topic/4137-pudding-photon-pudding-bootloader-unlock-updated-8302011/
Use at own risk. ???
Can u get into rsd mode and flash 154_5 sbf
Sent from my MB855 using xda premium
Important files
Thank shabbypenguin for those
If you can get into rsd mode and connected/recognized in rsd lite you should be able to flash one of those sbf files and return to stock.
I read the instructions carefully! It said to put the oven on 350 degrees for 10mins but for some out of this world reason I put it on broil and let it cook for 20mins :/
Sent from my MB855 using XDA App
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
enzyme said:
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
Click to expand...
Click to collapse
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
SOLVED!!! THANK YOU EVERYONE!
KTT16 said:
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Click to expand...
Click to collapse
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
enzyme said:
SOLVED!!! THANK YOU EVERYONE!
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
Click to expand...
Click to collapse
1) Format system is in the "mount" options. Although it's unneeded to flash a ROM. Personally I just wipe data/factory reset and then wipe cache and have zero issues. Others may tell you different though.
2) "Install .zip from SD Card" then select whichever .zip you're looking to install.
Sent from my MB855 using xda premium
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Flashing the 198_7 sbf unroots and relocks, so you're back to square one.
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Reboot into stock recovery, when you get the recovery logo thing push both volume up and volume down at the same time to get the recovery options. Then do a factory reset and it should boot for you. After that, root and unlock again. And you didn't have the Market because you forgot to install Gapps...
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
The reason cm7 didn't have the market is that you needed to flash gapps. Try doing a hard reset. http://www.hard-reset.com/motorola-photon-4g-hard-reset.html That should do it.
try the 154 sbf
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
i had the same problem i think and was going thru boot loops but some one told me to start into recovery when you try you get that ? android screen from there hold down volume up and down at same time then wipe phone booted up fine after that.
It worked like a charm. Thanks. I'm still very new to android and hate to admit it but will be running into problems like these again. The best way to minimize it for me is, not only follow certain directions correctly to get out of these binds, but to understand them.
- So theres an image of the stock ROM stashed away on the phone regardless? And it can be accessed only via the stock recovery? Because after I succeeded in flashing cm7.1, I did a factory reset once from settings>privacy and that restored me to a fresh CM7.1. The factory reset from settings>privacy and in CWM is the same, but both different from the factory reset via STOCK RECOVERY?
- Also what would be the correct method to go from one custom ROM to another? Would it be this? :
(in CWM)
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Or can I just jump to install from zip ?
- Also regarding SD Storage (internal), only holds storage files? So on any fresh ROM there shouldn't be anything in that partition relating to that new ROM yet right? So I can delete things without worry?
You should not have to reboot into recovery, once your wipes are complete, normally you can just flash your ROM of choice in the same recovery session.
Before I flashed anything I would make a backup with CWM so you don't have to keep rooting and unlocking. You can just restore your backup.
Sent from my MB855 using xda premium
After flashing 198 7 sbf, all u need to do is flash derpunlock not go through oem unlocking, then reflash recovery.
Simple generic process for going between roms (assuming already unlocked + cwm recovery flashed; process may be different for some roms, always make sure to read directions, but this is the general concept)
1. Download rom (and gapps if necessary) and put on your sdcard
2. Boot into recovery and make a nandroid backup
3. You made a nandroid backup right?
4. Secure your nandroid backup (move it to your pc or something).
5. You know where your nandroid backup is right?
6. Wipe data/factory reset.
7. Install zip from sd (flash), choose the rom.
8. Reboot system.
At this point your rom should be all set. If for some reason you don't like it, simply boot into recovery and restore your nandroid backup. You can even make nandroid backups of various roms if you want to swap between them for whatever reason.
I don't understand what is it that I might be doing wrong, I root the tablet, have bootloader unlocked, and install Dualrecovery. From TWRP recovery I wipe Dalvik cache, Cache, System, and Data. Install PAC Rom Castor and GApps using TWRP, all seems to go well, no errors present themselves. Then I reflash "TabZ2-lockeddualrecovery2.8.21-RELEASE.flashable" to keep the recovery intact before I attempt to boot into system per their instructions after installing a custom ROM. I wiped Dalvik and Cache before I reboot and once it goes away from recovery nothing occurs just my tablet remaining in flash boot which is a good thing so I can start all over again since obviously something went wrong and just use flashtools to get back to an old stock firmware. I have a SGP512. Any help is appreciated, thanks.
Edit: Even tried it w/o wiping system and same results just doesn't boot.
D03035790 said:
I don't understand what is it that I might be doing wrong, I root the tablet, have bootloader unlocked, and install Dualrecovery. From TWRP recovery I wipe Dalvik cache, Cache, System, and Data. Install PAC Rom Castor and GApps using TWRP, all seems to go well, no errors present themselves. Then I reflash "TabZ2-lockeddualrecovery2.8.21-RELEASE.flashable" to keep the recovery intact before I attempt to boot into system per their instructions after installing a custom ROM. I wiped Dalvik and Cache before I reboot and once it goes away from recovery nothing occurs just my tablet remaining in flash boot which is a good thing so I can start all over again since obviously something went wrong and just use flashtools to get back to an old stock firmware. I have a SGP512. Any help is appreciated, thanks.
Edit: Even tried it w/o wiping system and same results just doesn't boot.
Click to expand...
Click to collapse
Your device will never Boot if you flash pac with nuts recovery. It causes to much Problems with cm based roms. So to rescue your tab you need Boot into fastboot and write "fastboot erase recovery" then flash this kernel http://doomlord.xperia-files.com/do...2U3RrS2VybmVsX1dJRkktdjAzXzE3LjEuMS5BLjAuNDAy
Do not reboot to system. Power of the device and then Boot into recovery (when you see the Sony logo and the LED light turns pink/amber/orange keep tapping/pressing VOLUME UP key). Then you will See cwm recovery. There first do a factory reset and Format system. Format system is in mounts and storage options) now flash PAC Rom and gapps and reboot to system now the device should Boot correctly. After the first boot do all settings then go to developer options and you will find expand reboot menu or something Luke this. Tick it and than hold the power button for some second tap reboot than bootloader (before connect the device with your PC) than use fastboot to flash the New recovery. Use one of these http://forum.xda-developers.com/xpe...wrp-cwm-philz-recovery-collection-z2-t3052676
For instructions to flash recovery look in the thread there are a step "Installation" if you need more help write me
rcstar6696 said:
Your device will never Boot if you flash pac with nuts recovery. It causes to much Problems with cm based roms. So to rescue your tab you need Boot into fastboot and write "fastboot erase recovery" then flash this kernel http://doomlord.xperia-files.com/do...2U3RrS2VybmVsX1dJRkktdjAzXzE3LjEuMS5BLjAuNDAy
Do not reboot to system. Power of the device and then Boot into recovery (when you see the Sony logo and the LED light turns pink/amber/orange keep tapping/pressing VOLUME UP key). Then you will See cwm recovery. There first do a factory reset and Format system. Format system is in mounts and storage options) now flash PAC Rom and gapps and reboot to system now the device should Boot correctly. After the first boot do all settings then go to developer options and you will find expand reboot menu or something Luke this. Tick it and than hold the power button for some second tap reboot than bootloader (before connect the device with your PC) than use fastboot to flash the New recovery. Use one of these http://forum.xda-developers.com/xpe...wrp-cwm-philz-recovery-collection-z2-t3052676
For instructions to flash recovery look in the thread there are a step "Installation" if you need more help write me
Click to expand...
Click to collapse
Thanks! I used Flashtools to flash over the recovery via fastboot and accessed the recovery to do the rest. I had no idea CM based ROMS don't work well that recovery or any other I haven't tried yet. Any suggestion on what recovery to use? So far CWM got me this far not sure if I should try others. Philz Touch seems to be more appealing and the same as CWM.
D03035790 said:
Thanks! I used Flashtools to flash over the recovery via fastboot and accessed the recovery to do the rest. I had no idea CM based ROMS don't work well that recovery or any other I haven't tried yet. Any suggestion on what recovery to use? So far CWM got me this far not sure if I should try others. Philz Touch seems to be more appealing and the same as CWM.
Click to expand...
Click to collapse
Use this one https://mega.nz/#!rI4y2bJS!VksDLNy_a8cy8x-VBviYRkTP2SdSBm7Rs9G445vUXCU
This is twrp but it works with cmbased roms.