Related
I rooted my device using Gingerbreak.
I have 2.2.2 installed out of the box. I installed CWM. I installed busybox.
Busybox failed. I tried all the versions that it contains.
I checked root status, and RootCheckBasic says I'm rooted.
I installed Flash ClockworkMod Recovery. It will not reboot to CWM.
It only reboots to the standard Android recovery.
I'm trying to install Bumblebee ROM 2.4.
Here are some things I am having issues understanding with it...
Backup current apps and their data with Titanium Backup (available in the Market). Is this required? The phone is new. I have nothing to back up.
Do a nandroid backup in recovery before doing anything else below.
And the nandroid backup is done with CWM? Again CWM won't reboot, only the standard Android recovery boots.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). I assume you wipe it all with CWM while in recovery?
If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
Does not apply to me
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet. Installing wiper.zip is done by sideloading using adb commands?
Install ROM zip (see below).
I assume this too is done by copying the zip to the external SD, then selecting update from SD card in recovery... right?
Please someone shed some light on this for me.
In standard Android recovery it says e3. I know on my Captivate I had to use Odin to install GB loaders to get it to work.
THANKS!
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
tvall said:
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
bulltproof said:
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
Click to expand...
Click to collapse
Oh, okay, um... are you using the reboot into recovery option in rom manager right after flashing?
After flashing what?
I reboot into recovery through rom manager and get:
Android system recovery <3e>
reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
_________________________________________________________
Android System recovery...
Do not pull out the battery!!
After hitting flash clockworkmod recovery, immediately hit reboot recovery
After hitting anything in CWM it did nothing more than reboot into the standard android recovery.
This phone has 2.2.2 on it. Problem? Probably.
I followed instructions at androidcentral and got it to work.
Needed Xionia_CWMA_12518.6_VM
Installed BACKside-IHO-VM670-11222011
using Xionia_CWMA_12518.6_VM_Recovery-signed
Had a little problem today and needed to activate the phone. BUUUUT......
the rom didn't allow activation.
So I installed Bumblebee. No go.
Then I tried [rom] basic stock rom.
Neither of these will let my phone boot. It gets stuck at boot.
Nothing happens.
I can still boot into Xiona_CWMA. But no roms will work.
PLEASE HELP!!!!
Dude i m noob, and i m facing same problem,
I did root with super one click soc, and it is rooted and i am using root needed apps,
But when i m trying to clobk work recovery (i did flashing CWR from rom manager and aft that i select boot from cwr option from rom manager) it just factory reset i did this 3time all time just factory reset, then i again did but while rebooting i click home button so it gave me same option which came to above member said some e3............
And i try to select any option from it with menu button it was not applied, and no use so i removed battry and place again and start then device started dont know more what to do, help
Sent from my LG-P500 using Android-HQ App
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Bullet if u found solution pls tell me too
Sent from my LG-P500 using Android-HQ App
bulltproof said:
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Click to expand...
Click to collapse
I believe that may be due to the newer display in your phone (I'm new to this device so I dont know much yet). From the little bit of information I've gathered, devices manufactured recently have a different display that requires a kernel that supports it. In the iho roms this is included, on others you'll need to flash a kernel right after the rom.
For the stock rom I can upload what I use if you need it. Its basically the one posted here just with the boot.img swapped with one from a nandroid backup I made before switching roms
I think you're spot on with that idea.
I loaded CM7 variant, and it worked.
My question is, how do I get another ROM on it if it has the newer screen?
I loaded different kernels that were supposed to fix it, but no go.
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.
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.
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
Have u tried these fastboot commands
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
Okay, I've done that and then I flashed CWM Recovery through fastboot. I then booted into CWM and flashed the jokersax's CM9 ROM and rebooted. What I still get is:
No OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Available Modes are:
1 RSD
2 Fastboot
3 NvFlash
etc. etc.
It isn't detecting an OS still, and I don't get a boot icon just that menu. What would you suggest?
I'm thinking of trying this: http://forum.xda-developers.com/showthread.php?t=1421522
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
1. Re: CWM wipe and spazzed out touch screen: Sounds like you erased your PDS partition. If you made a back up, flash it. Otherwise search for a thread titled PDS Partition Fix (or something similar) here in the Q&A section for an alternative fix.
2. I don't recall if doing the PDS fix will also fix the missing boot logo. If not, you can find a stock replacement in the Themes section. You're looking for logo.bin.
That fixed it, thanks! I did a full wipe of those partitions then restored from my CWM restore. That didn't fix the screen but I tried that fix you suggested and everything is perfect now. Thanks for the help.
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.