Database Info

Bricked (fixed)

I'm not a noob.
Here's the situation.
I was experimenting with themes with Haykuro's 5.0.3H apps to sd and I ended up with a looping HTC screen. I did a wipe and tried to perform the update again. Same. I tried a fastboot restore... stuck at android for over an hour.
Tried fastboot flash update.zip and I get
"writing 'update' ... FAILED (remote: partition does not exist)
I tried putting RC33 1.42 on a blank SDCARD and applying update... and it's stuck at the boot screen.
EDIT::: I got 502Hr3 GlossSuite back on there that I made... but the appstosd wasn't working and made my phone loop at the "htc" boot up.
03:00AM Just downloaded Partition Manager 9 and will try to reformat/repartition my sdcard and start appstosd over from scratch.
Did I just paperweight my G1?
08:00 4/21/09 FIXED!!!
Binary100100 said:
Right... so here's the story as well as I can remember it.
I made a theme for 5.0.2H AppsToSD GlossSuite and flashed it. Made 3 calls with it and then did a backup with nandroid. Then, being proud of my achievement, posted my work and it was downloaded over 20 times.
I decided (for some reason that I can not explain... maybe lack of sleep after working on this for so long) that I'll go back to RC33. Flashed the RC33 Apps to SD rom and radio back and used RC33 and then used the apps to sd app for the apps to sd. I had RC33 installed and working for about 2 hours while I tried to cook up a few more changes (launcher... clock... etc). Then wiped and tried flashing back to the new rom. Everything worked. Flashed the new radio. Everything worked. Followed the instructions for apps to sd for haykuro builds... rebooted... looping HTC boot screen.
I tried a wipe... looping.
Tried a nandroid restore with several of the backups that I made.
Stuck at the splash screen and I left it there for over an hour.
I got impatient and pulled the battery and tried another flash from a different backup. Same. Both were RC33. So I tried with the Haykuro backups... same.
I moved RC33appstosd.zip to the root of my sdcard and renamed it update.zip.
Flashed... looping Android screen. Tried a fresh 128mb sdcard with update.zip. Same.
I tried recovery fastboot flash update.zip and got "writing 'update' ... FAILED (remote: partition does not exist)
Then made my first post up above.
Did "fastboot erase system -w" from korndub's suggestion.
Then fastboot flash my .img's. I got the looping Android again.
I was about to give up when I downloaded the REGULAR RC33 to my sdcard, renamed it update.zip, updated and it FINALLY booted up. It was at this point I was finally able to see a homescreen.... so I figured it had to be something with the apps to sd.
But now there was another problem... I would get android.phone (or whatever) force close error everytime I would get a call. I couldn't place calls either. Several people were experiencing the same problem that flashed my rom and needed help. But if it was a problem with the rom then why was I experiencing it on RC33? Plus... I made a calls when I had in installed on my phone at the beginning. It was very strange. But I had the problem with RC33.
So I tried to repartition my card with Paragon Partition Magic 9 and it could not repartition my card! I tried to just repartition it in Windows (XP) and it worked. I tried Partition Magic again... still gave me errors and wouldn't let me do it! So it must be a problem with my SDCARD. I decided to give a very old program that i had stored in a box a try called Copy Commander 9 (I'll gladly remove the file upon request... just pm me... I just want to help out anyone that has issues with the paritioning process. This is a trial version but you can boot from CD and fix your partitions).
I booted from CD and it fixed my partition problem right away!
I did a fastboot erase system -w in recovery to wipe and reflashed RC33 and the phone was working again. Calls and all. Not taking any chances... updated (in this order)
RC33 > RC33 Apps2SD > RC33 Apps2SD Gloss Suite
I'm scared to go back to 5.0.2H Apps2SD now.
Sooooo... with all of that said... where the hell did I go wrong? I backup with nandroid everytime before I wipe and update. I boot up to confirm they are working... mount the sdcard so I can rename the files to the firmware, time, and date of the backups. And yes I wipe everytime I flash a update.zip
I'm still convinced that it was the apps to sd and/or the partition... but how would that explain the force closes for calls on RC33???
Anyway... feel free to comment but fyi I'm good now (or at least I feel like trying Haykuro's build again)
Click to expand...
Click to collapse

you dont fastboot flash update.zip....
try this...
fastboot erase system -w
then flash the system image back.
fastboot flash system system.img
fastboot reboot

korndub said:
you dont fastboot flash update.zip....
try this...
fastboot erase system -w
then flash the system image back.
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
sending 'system' (70038 KB)... OKAY
writing 'system' ... OKAY
7:55 PM
8:05 PM still hanging at my splash screen.
NOTE: I've already tried flashing my nandroid backups (userdata.img, system,img, boot,img) and had no luck.
Trying again...
fastboot erase system -w
erasing 'system'... OKAY
erasing "userdata'... OKAY
erasing 'cache'... OKAY
8:06PM
fastboot flash system system.img
sending 'system' (70038 KB)... OKAY
writing 'system'... OKAY
8:08PM
It boots up to flashing android and loops.

Looks like your gonna have to start back at RC29 re-root and start all over.

yep..may be the only way to get it working...start fresh at rc29 re-root and re-update

jjjackson56 said:
Looks like your gonna have to start back at RC29 re-root and start all over.
Click to expand...
Click to collapse
if u can access the bootloader there is always hope as so i have heard in the forums
i dont know mcuh about it
but from the countless threads i read while in class and not listening to my professors...if u can access the bootloader there is always hope. just flash the dreaimg.nbh file and start all over...better than a looping phone...
and for now
i would suggest dont expirement with themes because the rom is already unstable as it is in the background...it may look like it works flawlessly but u must rmr this a port form a magic phone...
hope this helps :-D

I had this happen to me this weekend. I just re-applied a known working update.zip from recovery and it solved my problem. I went thru 10 nandroid backups before I tried that too

I've had this happen a couple times while developing my theme for RC33. Just flash DREAIMG.nbh and start from scratch.

TheDudeOfLife said:
I had this happen to me this weekend. I just re-applied a known working update.zip from recovery and it solved my problem. I went thru 10 nandroid backups before I tried that too
Click to expand...
Click to collapse
Well... I eventually got it working again... kinda. But I think it is a problem with my /system/sd or my ext2 partition because when I try to move my apps to sd (btw... there are already several on there) it loops at the htc screen. So I am downloading Partition Manager 9 now and I'm going to try to repartition/format my sdcard and see if that corrects the problem. Luckily I backed ALL of my apk's to my sdcard earlier that day. It's strange though because the only thing that I can think of that messed it up was the appstosd app that I used. It worked at first... I did a backup (even labled it)... rebooted... then it started looping. So... I'm going to start Apps to SD from scratch and that should fix my problem.
But why is it that when I tried to flash BACK to RC33 it was being pissy at me? I don't even know if I'll be able to flash back now.

When i went to the haykurus from the jf rc9 version it stood solid still at the htc for a good 15mins, then suddenly WHAM woke up and asked for pin code.. When i had completed the "setup" i tried a call + menu + hangup reboot.. And it worked like normal in boot, took no mere than a few seconds.. So first time can be LONG, funny thing is, its not always like that, tried a few versions of the haykuro, sometimes its only hanging for a 5 mins, other 10..

FIXED
Right... so here's the story as well as I can remember it.
I made a theme for 5.0.2H AppsToSD GlossSuite and flashed it. Made 3 calls with it and then did a backup with nandroid. Then, being proud of my achievement, posted my work and it was downloaded over 20 times.
I decided (for some reason that I can not explain... maybe lack of sleep after working on this for so long) that I'll go back to RC33. Flashed the RC33 Apps to SD rom and radio back and used RC33 and then used the apps to sd app for the apps to sd. I had RC33 installed and working for about 2 hours while I tried to cook up a few more changes (launcher... clock... etc). Then wiped and tried flashing back to the new rom. Everything worked. Flashed the new radio. Everything worked. Followed the instructions for apps to sd for haykuro builds... rebooted... looping HTC boot screen.
I tried a wipe... looping.
Tried a nandroid restore with several of the backups that I made.
Stuck at the splash screen and I left it there for over an hour.
I got impatient and pulled the battery and tried another flash from a different backup. Same. Both were RC33. So I tried with the Haykuro backups... same.
I moved RC33appstosd.zip to the root of my sdcard and renamed it update.zip.
Flashed... looping Android screen. Tried a fresh 128mb sdcard with update.zip. Same.
I tried recovery fastboot flash update.zip and got "writing 'update' ... FAILED (remote: partition does not exist)
Then made my first post up above.
Did "fastboot erase system -w" from korndub's suggestion.
Then fastboot flash my .img's. I got the looping Android again.
I was about to give up when I downloaded the REGULAR RC33 to my sdcard, renamed it update.zip, updated and it FINALLY booted up. It was at this point I was finally able to see a homescreen.... so I figured it had to be something with the apps to sd.
But now there was another problem... I would get android.phone (or whatever) force close error everytime I would get a call. I couldn't place calls either. Several people were experiencing the same problem that flashed my rom and needed help. But if it was a problem with the rom then why was I experiencing it on RC33? Plus... I made a calls when I had in installed on my phone at the beginning. It was very strange. But I had the problem with RC33.
So I tried to repartition my card with Paragon Partition Magic 9 and it could not repartition my card! I tried to just repartition it in Windows (XP) and it worked. I tried Partition Magic again... still gave me errors and wouldn't let me do it! So it must be a problem with my SDCARD. I decided to give a very old program that i had stored in a box a try called Copy Commander 9 (I'll gladly remove the file upon request... just pm me... I just want to help out anyone that has issues with the paritioning process. This is a trial version but you can boot from CD and fix your partitions).
I booted from CD and it fixed my partition problem right away!
I did a fastboot erase system -w in recovery to wipe and reflashed RC33 and the phone was working again. Calls and all. Not taking any chances... updated (in this order)
RC33 > RC33 Apps2SD > RC33 Apps2SD Gloss Suite
I'm scared to go back to 5.0.2H Apps2SD now.
Sooooo... with all of that said... where the hell did I go wrong? I backup with nandroid everytime before I wipe and update. I boot up to confirm they are working... mount the sdcard so I can rename the files to the firmware, time, and date of the backups. And yes I wipe everytime I flash a update.zip
I'm still convinced that it was the apps to sd and/or the partition... but how would that explain the force closes for calls on RC33???
Anyway... feel free to comment but fyi I'm good now (or at least I feel like trying Haykuro's build again)

I do know that there is some kind of a bug in the phone.android.com thing in about every build there is, including official ones, and I don't think it has become completely resolved.
I have gotten it when I lock onto a carrier, then restart my phone in an area where that carrier has no signal. Others have had it when ending a call, as in your case. Others have reported it when they've changed providers.
Sometimes, a new sim fixes it, and sometimes it doesn't.
I know I didn't give any real answers here, but thought I would give you a heads up that it isn't unknown. I was just lucky enough to find something that was a solution for me.
When I called tech support, (T-Mo), and told them what fixed it for me, they were very glad to have one solution to at least try, because they do get this issue, and often times, they end up sending a new phone, because they don't know how to fix it.

kathi17 said:
I do know that there is some kind of a bug in the phone.android.com thing in about every build there is, including official ones, and I don't think it has become completely resolved.
I have gotten it when I lock onto a carrier, then restart my phone in an area where that carrier has no signal. Others have had it when ending a call, as in your case. Others have reported it when they've changed providers.
Sometimes, a new sim fixes it, and sometimes it doesn't.
I know I didn't give any real answers here, but thought I would give you a heads up that it isn't unknown. I was just lucky enough to find something that was a solution for me.
When I called tech support, (T-Mo), and told them what fixed it for me, they were very glad to have one solution to at least try, because they do get this issue, and often times, they end up sending a new phone, because they don't know how to fix it.
Click to expand...
Click to collapse
well... i suppose it could make sense because my sim card needs to be replaced. the poor thing has played musical phones for about 7 years now. LOL.

make sure card is formatted correct "FAT32" ifso reformat anyway! then try again. if propblem persist\. re flash "dreaim.nbh" rc29

[Q] Boot loop on evo with calkulin

Sorry if this has been discussed but apparently the forum search isn't working and these suggested threads aren't exactly what i'm looking for, although i did see one that talks about Fresh 0.2 and boot loop being caused by it.
So anyway, I have this under control, i would just like some answers. Here are my questions as simple as i can ask them:
I would like to get the notification bar included in the calkulin 2 v1.8 rom, it is very nice looking, does anyone know where i can get it without having to flash the rom on my phone?
What causes boot loops(at least only after flashing a rom or restoring files)?
What wipes should I be doing?
Is there something bad about using unrevoked to root your evo?
Is there any similar probs with MyBackup Root?
Here is some information you might find useful:
I rooted with unrevoked 3.2.1 which unlcoks NAND for EVO with froyo(which i have) so yes my hboot screen says S-OFF
I also switched from clockwork to amon ra 2.3 due to some issues.
I have flashed azrael on and it worked with no probs, even with only wiping CACHE, DATA, and DELVIK CACHE.
I did the same wipe for calkulin the first time.
Calkulin starts, i can use the phone. Then I restore apps and data with MyBackup ROot, and it says to reboot.
Once I reboot, the loop begins until i pull the battery(i don't know for sure, but I've never let it go beyond 10 minutes)
So I have restored my nandroid backup and everything is peachy.
Now i tried wiping ALL USER DATA/Factory reset plus the 3 mentioned above(and btw, i don't have an SD ext partition the wipe always says skip)
After flashing calkulin for the second time, i restore files again, reboot, and get the same problem.
I managed to find a thread where this was occurring with CM7(which i have not looked at so i don't know anything about it). Just give some suggestions and veterans and devs please figure this out! this is a big inconvenience!
It's probably worth mentioning that mybackup root worked with azrael(i think i heard that some apps aren't supported in every rom).
Again, I don't get this problem with the original rom or azrael. I was thinking of using the calkulin format all wipe, but i read that it's the same as doing the 4 i did(plus the sd ext, but i don't have that partition so it would be skipped anyway). Please someone figure this out thank you!
ps. i strongly think its mybackup root, but then again, i haven't tried rebooting without restoring anything and i haven't tried titanium backup either.

Rooted - Now no 4g/3g/1x. What gives?

Ok, so I purchased my Thunderbolt yesterday, and of course, first thing's first. Root.
I am familiar with the OG Droid, and rooted it using the RSDLite method. I am also familiar with using ADB to push/pull files, as well as using apkmanager to modify apks, primarily for themeing purposes, but I do a little bit of XML editing, as well.
I am also familiar with my wife's HTC Incredible, and I have rooted it (Using the UnRevoked method) and flashed a few custom ROMs to it, as well.
I took on the manual rooting instructions for the Thunderbolt, and all went easy peasy, other than being a bit time consuming. I thought I had it all worked out, and was running Plain Jane (flashed using CWM Recovery) and with the recommended baseband/radio (flashed from hBoot).
But I noticed when I left my house (where I was using wi-fi the whole time) that I wasn't getting any 4g/3g/1x service whatsoever. I had cell signal, full bars in fact, but no data transfer.
So, I tried flashing a few different radios, and I just ended up flahing BAMF Sense 3.0 with the mr2 baseband update for gingerbread ROMs.
I still have the same problem. I get cell reception, but no data transfer. I can get momentary data if I tell the software to check for a software update. 3g pops up, it checks for an update, and when it is done, 3g goes away and I once again have absolutely no data transfer. Can't surf the web, or use any apk that requires data.
Anybody have any pointers? I have made sure that the mobile network option is checked in the settings. Aside from that, I have no clue where to begin.
Any help is greatly appreciated! TIA!

Only thing I can think of is the radio. I'm using the .627 radio from the inj3cttheory rom post in dev section.
http://forum.xda-developers.com/showthread.php?t=1155986

Hi, and welcome to the tbot community!
a few quick questions,
prior to flashing did you check MD5 sums on both the radio and rom?
and did you delete the PG05IMG.zip file you flashed during the rooting process from your sdcard?
also this may sound like overkill but did you wipe everything (data/cache/dalvik/bat-stats) 3 times?
i would recommend re-downloading both the rom and the radio and check MD5 sums. then put them on your sdcard and make sure their is only one PG05IMG.zip on the root of the sdcard. this next stuff is important; connect phone to your computer and verify that adb recognizes your device. then reboot into recovery and wipe data/cache/dalvik/bat-stats 3 times each. and after that re-flash the rom first, let it do its thing as normal. after the rom is installed do not reboot just stay in recovery. at this time you need to use adb to reboot into the bootloader to flash the radio. after that just reboot like normal

Sent from me, using this app on this thing.

blazednova said:
Hi, and welcome to the tbot community!
a few quick questions,
prior to flashing did you check MD5 sums on both the radio and rom?
and did you delete the PG05IMG.zip file you flashed during the rooting process from your sdcard?
also this may sound like overkill but did you wipe everything (data/cache/dalvik/bat-stats) 3 times?
i would recommend re-downloading both the rom and the radio and check MD5 sums. then put them on your sdcard and make sure their is only one PG05IMG.zip on the root of the sdcard. this next stuff is important; connect phone to your computer and verify that adb recognizes your device. then reboot into recovery and wipe data/cache/dalvik/bat-stats 3 times each. and after that re-flash the rom first, let it do its thing as normal. after the rom is installed do not reboot just stay in recovery. at this time you need to use adb to reboot into the bootloader to flash the radio. after that just reboot like normal
Click to expand...
Click to collapse
Thanks for taking the time to write up your response.
To answer a few of your questions, I did check the MD5 for both the radio and the ROM, and found them both to match.
I did wipe thoroughly, at least 3 times, in fact I went so far as to go into the "Mounts" section of CWM Recovery, and I wiped everything (Data, Cache, System...) from there as well (save it be for the SDCard).
What I did NOT do, however, is ensure that the phone rebooted directly to the bootloader. Instead, I selected "reboot system now" from recovery, and just tried to catch the boot cycle to put it into the bootloader, but that failed.
I will re-wipe everything, and re-install the ROM, and this time I will make sure to reboot using adb directly into the bootloader and see how things go from there.
Thanks for the pointers. I will report back once I finish.
If that doesn't do it, I suppose I'll have to try some different radios...
EDIT: I also did delete the radio/baseband update from the SDCard after booting back up.

If that doesn't work it may be your SIM card. There have been reports where SIM cards randomly fail and data is unavailable. I don't think it has anything to with the rooting or flashing process that causes SIM failure. You may have to unroot to get SIM replacement though.
Sent from my ADR6400L using Tapatalk

OK, I went through the entire process over again, this time ensuring that I rebooted to the bootloader immediately after installing the ROM and letting it install the mr2 radio/baseband.
Results = no love.
Still no 4g/3g/1x.
I am now contemplating going completely back to stock to see if things work in stock form, and if they don't, then I suppose the sim card may be the issue.

OK, quick update. After little contemplation, I decided that reverting back to stock-unrooted was the most logical next step to take. I followed the steps outlined in the following thread: http://forum.xda-developers.com/showthread.php?t=1009423
I only flashed the 1st file (PG05IMG_MR1_no_hboot.zip), and left the bootloader alone. So, as far as I understand, I still have an unlocked, s-off bootloader.
I now have data back.
My next question is, am I able to gain root on the software that is currently on the phone (1.13.605.7) without having to do any downgrades? Or are the exploits only functional on an older/downgraded build?
And my other question is, are there any ROMs in an RUU format that I can simply flash from my bootloader since it's still unlocked with s-off?

Success!
After reverting back to stock, I decided to attempt the rooting process again. Took the exact same steps as the first time, only this time I made sure I allowed the data connection to connect between each downgrade/upgrade/reboot before continuing on with the next step. I'm not sure if that's what made the difference, but it really is the only thing I changed. I didn't redownload any of the files. Simply used the same ones I used previously.
Anyway, I hope this thread serves as an aid to anyone else that might run into this issue.
Thanks for all the suggestions and help.

Congrats! Now get to flashing some awesome ROMs!
Sent from my ADR6400L using Tapatalk

MrHawaii said:
Congrats! Now get to flashing some awesome ROMs!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Done, and done. Currently running das BAMF RC4.9 with the MR2 radio. So far, running awesome!

Problems after getting back to stock ROM from CM7

Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up

Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.

CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.

I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.

A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.

Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.

Still have to restart the phone every 1-3 apps installed. This is driving me crazy

Flashing wrong Recovery (hboot 2.22) wiped whole phone (including sd-card)

Hey folks,
have a huge problem here. I think i erased all the data of my girlfriend's phone -.-
I just wanted to clear her phone by setting it up with a custom stock rom withput bloatware.
I started to unlock the bootloader and flash a new recovery because i wanted to do a nandroid backup and use titanium to backup her data. But the problem started here. Her phone had the 4.4.2 OTA update --> HBoot 2.22 but I flashed TWRP 2.7.0.0 instead of 2.7.0.5 because i didn't know the fact that the partition layout changed. After flashing the recovery the internal sd card couldnt be found and twrp said "no OS installed" when i tried to reboot to the system. Well, the phone did boot to the system, but i think it made a background factory reset i didn't want to do ...
So now i had a clear System running, no apps, no contacts, nothing. At this point I didn't look at the sd card if the data there is erased, too.
I thought, when i flash a recovery which finds the sd card, maybe the system will be restored as before this procedure. So i flashed twrp 2.6.3.0 but again, no sd card. After that i tried cwm 6.0.3.6 (because i didnt know that there was a 6.0.4.7 ...) and cwm accepted the card. So i booted again into system but still there was a clear stock rom, with ... nothing.
THEN I looked into the sd card and ... nothing. Empty, everything got deleted, only the new made folders where there. No Pictures, no Music, nothing.
My girlfriend gonna kill me ...
I tried to rescue the data from the sd card, but different apps found nothing then the data, that is already on the sd card. No old pictures or old music. Thanks to MTP, i can't run a datarescue at my pc (or can i?).
Do you have any idea what i can do now? Is there any chance of getting the data from the sd card back? Or better, getting the old app data back?
Please help me guys, you are my last hope.
greetings,
patrick

best of luck to you my friend
Im in the same exact boat to the T !!
Did the same thing almost identical to you , all because the development is so shabby and unclear with this particular phone its pathetic.
twrp website shows the latest recovery.img as 2.7.0.0 No mentioning of flashing a newer version
Theres only one thing at this point you can hope for Find the stock 4.4.2 ruu utility and run it... or get her a new phone.
Ive been at my pc for 8 hrs going blind and im done ill toss it before i spend another hour searching for a fix
I have multiple posts Noone cares here.
And i dont believe htc has the 4.4.2 ruu out yet

Well, my problem was not to get the phone running, because it did "repair" itself.
My problem is the lost data

Hi Patrick
Having no backups and starting to change things in software is always a bad idea. Mobile phone, PC, etc.
On the other side, there are very nice tents today in case your girlfriend has locked you out of your home now
Consider it from this side, you tried something and bungled :crying: the phone/data - hopefully others will read this before they install the "old" recoveries on their new Hboot.
But I totally agree with you, these unofficial versions of the recoveries are really hard to find. As I was looking for the download link I've chosen the way through the xda thread.
regards

Thanks for your thoughts
But luckily my girlfriend doesnt lock me out of home, because i had the backup from November
Since then we didn't have made any greater activities so no real important pictures were made since then.
I thught of making a "newbie friendly" thread with important information about hboot 2.22 and the "hidden" recovery's from twrp and cwm.
Maybe this can help others to prevent such mistakes I did in the past.

Klivarre said:
Thanks for your thoughts
But luckily my girlfriend doesnt lock me out of home, because i had the backup from November
Since then we didn't have made any greater activities so no real important pictures were made since then.
I thught of making a "newbie friendly" thread with important information about hboot 2.22 and the "hidden" recovery's from twrp and cwm.
Maybe this can help others to prevent such mistakes I did in the past.
Click to expand...
Click to collapse
Would be good to have this info in a sticky, as these posts can get buried easily.
Sent from my GT-I9000 using Xparent Green Tapatalk 2