Related
SOLVED it myself - read below:
The super quick version:
During an attempted downgrade from 02 2.1 6941 (it was buggy as hell) back to ATT 1.6, I tried a method someone posted involving clockwork 1.8.1.7. Unfortunately, clockwork can only burn .zip clockwork formatted roms (you cannot simply rename a pkg a zip). All attempts to switch back to any other recovery program simply resulted in a black screen after selecting update - many recovery roms were tried. So I was stuck with no way to even try to burn a regular pkg rom and a broken clockwork (1.8.1.7 "works" but with errors).
TLDR: Black screen after "press camera button to update" on all recoveries except clockwork 1.8.1.7 on 02 1.6 4399.
Solution:
Installed clockwork formatted rooted 4399
Installed older recovery rom I found
I can provide links to these later. I don't have them on me at the moment.
If anyone has any idea how to solve FOTA name mismatch, or even wtf it means, let me know.
WOuld be great if u could tell the forum what u did
You may not be alone
r00tcause said:
Solved my own problem after hours of trial and error - no thanks to anyone here.
Click to expand...
Click to collapse
The Streak community seems to be pretty small at this time. Until we have a bigger user base we are all kind of breaking new ground. People might not have had the same experiences as others, such as yourself, so maybe you could share your story and help someone in the future.
drgopoos said:
WOuld be great if u could tell the forum what u did
You may not be alone
Click to expand...
Click to collapse
I was busy raging at the time.
I am *still* stuck on o2's OS (but 1.6 which works fine instead of the seriously bugged 2.1, which worked "ok" at first and got so buggy that it wouldn't allow me to answer incoming calls) but at least my recovery is no longer broken.
I can't swap back to ATT though due to a "FOTA name mismatch", whatever the hell that is.
The black screen recovery error seems to be caused by the ROM itself. Certain recoveries simply do not work on certain builds. It seems as though pretty much all of them failed with the build I had. However, I found an older recovery (smaller than the rest at 2.7mb) and used that along with a rooted ZIP format (clockwork) version of 4399.
It was really just about finding the right files and the right combination.
I hope I can upgrade to the ATT froyo when it gets here without issue. For now, I am staying with what works.
Download the attached recovery, flash it and you should be able to update any official rom.
crash6 said:
Download the attached recovery, flash it and you should be able to update any official rom.
Click to expand...
Click to collapse
**I looked through my recovery roms and I had already tried THAT EXACT ROM, so perhaps stop making assumptions, eh?**
The only recovery that worked was the 2.7mb one. I tried many others. They all resulted in a blank/black screen after selection.
The files I used to fix the issue are linked below.
The first is a zip/clockwork version of O2's 4399 build which clockwork can burn. The second is the stock 4399 recovery (2.7mb).
4399-update-streak-stock-rooted-signed-clockwork.zip - 80.1 Mb
recovery.stock4399.img - 2.7 Mb
*This fixed the black screen on all recovery roms except clockwork 1.8.1.7 issue. It won't do a thing for FOTA mismatch.
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
I have an odd problem. My Dell Streak will boot but once it gets into the OS none of the buttons are responsive. It is not frozen however. I've recalibrated the touchscreen but that does nothing.
However, the controls work when I am booted into recovery and the screen before fastboot.
The person I bought it from had tried to install StreakDroid but I'm not sure how he went about it. I followed the guides, flashing the correct amss and dsp. But I have the same issue.
I'm wondering what the problem could be. Should I try and flash the original Dell rom back on first and see if that works? It is just odd that everything works except when it has booted into Android.
I'm going to assume you have a custom recovery on there. If so, make a nandroid backup, flash a stock recovery, update via the matching pkg file, flash StreakMod recovery, then restore your nandroid backup. That will ensure all the firmwares "match", which could be causing your problem. It sounds like you aren't sure of the history of the roms and such on this phone. This will start you out at square one without losing your custom rom and settings. Certainly couldn't hurt.
I've tried to install the stock pkgs (I tried 360 and 319) but both stop working at the end of the install. How long is the install meant to take? Because I've left them for half an hour at the end but it hasn't completed
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
theskyisoutthere said:
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
Click to expand...
Click to collapse
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
attempted to unroot
aicjofs said:
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
Click to expand...
Click to collapse
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
theskyisoutthere said:
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
Click to expand...
Click to collapse
If you have touch in Android install this https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager push your backup and use the program to make the open recovery script for you.
no touch anywhere. and no wifi!
Like I said no wifi and no touch at all anywhere So going online Iis a no go. I can use a mouse on the android system. Also I beleve my backup firmware is what caused the issue with the touch. Again this is a nabi 2 so now its been reset no file manager either access a apk from the sdcard if I could get the apk for that.
update
browser loaded the twrpmanager apk with that installed stock image now wifi works but no touch still what am I missing with the touch? Trying the stock update to see if that corrects anything I doubt it though
over post sorry
I know I am over posting on my own thread... sorry about that.
Had a thought. Since I am not great at describing what I need to accomplish here, try to work with me on this.
I need to just complete start over GO FOR BROKE format and push out the rom with adb How can I get started to do this and what do I need?
I feel that something in the touch input is not working based on some part of the rom is hosed. even tried the original recovery gives that android error icon thingy and I see nothing till she restarts nothing changes.
OK if you want to go for broke... You have to have an external SD card for this. TWRP must be installed
Hook Nabi up via USB can be in Android or TWRP
1) Download this: Nabi 2 stock
2) Unzip the NABI2STOCK.zip
3) Go here: http://forum.xda-developers.com/wiki/Fuhu_nabi_2
4) Grab either the 2.0.5 or 2.1.27 stock rom
5) Put the downloaded ROM zip in the "install" folder that was made in #2. Dont unzip, just download it straight to the install folder
6) Run 205.bat or 2127.bat depending on which ROM you chose.
The script will extract the ROM from the zip, copy the stock ROM to your external SD card, create an openrecoveryscript that will format system, format data, and restore Boot and System partition. Data will be left blank. This erases everything, except hidden partitions and recovery partition.
downloading will update when its done
downloading now will update when I run it. I hope things fixes it. as I have hosed it so far.
I get an error
I get an error
mkdir: can't create directory /external_sd card/twrp/backups/015d2a50211c1a19/abcdstock or something like says directory does not exist odd error it went thought its cycle and exited after that.
I do have an external sd card in it and it is working. did not know if that was an sd card error or what
no touch still
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
theskyisoutthere said:
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
Click to expand...
Click to collapse
It seems hardware now, but it is odd that touch went out when you were doing things to it. Still under warranty? Have you taken it apart and seen if anything is wrong?