Related
Im running a rooted Desire with LEEDROID rom 2.2b
I have superuser access (double-checked through terminal) and everything is pretty much working.
However, in Rom Manager if i go to fix permissions i get the error saying "An error occurred while running privileged commands".
Ive installed busybox through Titanium and double checked everything, yet I cant get the permissions fixed. This is especially nerve-wracking since i keep getting "Force Close" errors with many applications and this should fix it.
Ive tried clean wiping and reflashing the rom but it didnt work. Ive also tried re-rooting with Unrevoked, but it didnt work.
Please advise.
A friend of mine had similar problems. I suggested he try S-OFF and everything was smooth sailing from there on-out.
Head on over here and just follow the instructions in this thread
zHk3R said:
A friend of mine had similar problems. I suggested he try S-OFF and everything was smooth sailing from there on-out.
Head on over here and just follow the instructions in this thread
Click to expand...
Click to collapse
I did S-off, however it got stuck after an hr on step 3. So I pulled out battery and rebooted and I got the Alpha-rev home screen and it shows alpharev in fastboot.
I then re-installed the rom and deleted all the data. But still i get the same stupid warning from Rom Manager.
Im going to kill someone soon.
Hi, ive just tried s-off and rooting my HTC desire so that I can flash custom ROM's, this is my first time doing this ever and ive been studying it for weeks, I cant say I was calm about doing it, in fact I was bricking myself all the way through, however it seems to have gone well other than one slight thing.
After careful study I decided to go with a video and step-by-step insturctions on the unlockr site, including links to all the required files.
I have the Revo Stock hboot now and also have clockworkmod on my phone, I followed the root instructions to the letter as well as follow the video, however decided to use clockworkmod first to make a backup and restore image to my sdcard first incase anything went wrong, I then installed the superuser.zip file, it said this all went fine and installed successfully and enjoy, after a reboot of the phone, I have no superuser in the apps menu ?
Tried installing it again, once again it said successful and enjoy, but still no superuser in the apps menu ?
If I wanted to just root my phone again now, im not sure which way to do it as I now have a strange hboot version on my phone ?
Im also new to these forums and wasnt sure if this was the right place to post this, any help would be greatly appreciated.
hi, post all info from hboot/fastboot screen
-Revolutionary-
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:10
HBOOT
(VOL UP ETC..............)
If is not working via recovery try to download it from market or push it manually(adv, qtadb)
Sent from my HTC Desire using XDA Premium App
Thanks, I had a look on market and was gonn ask if that was the same superuser, so although I dont have the app yet am I pretty much still routed ?
I was gonna run unrevoked 3 last night to try and root a different way but thought i'd wait for a reply on this thread first, should I try that or is there no need ?
Just tried downloading superuser onto my phone then thought I test it, so I downloaded titanium backup too, when I ran titanium it said unable to gain root access, this program will not work, any clues anyone ? My info is above, and suggests that I'm rooted.
After using Revolutionary you have to flash this superuser.zip from recovery to get root access (you didn't do this, did you?:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efgh-signed.zip
So uninstall superuser and Titamnium Backup, boot into recovery, flash the superuser.zip and then try again.
Yes I did do this, my first post clearly states I tried this twice, then rebooted the phone, went into the apps menu and no superuser, so I tried to manually download superuser from market.
Although it says its installed and completed successful / enjoy, its like the root part of the whole process isn't taking effect ?
You may not have enough free space on the /system partition and although the .zip reports a successfull installation, it may not install.
Seanie280672 said:
Yes I did do this, my first post clearly states I tried this twice, then rebooted the phone, went into the apps menu and no superuser, so I tried to manually download superuser from market.
Although it says its installed and completed successful / enjoy, its like the root part of the whole process isn't taking effect ?
Click to expand...
Click to collapse
Okay sorry missed that. I recommend to ask Revolutionary in their IRC channel.
Sent from Sandvold's ICS using Transparent XDA App
TVTV said:
You may not have enough free space on the /system partition and although the .zip reports a successfull installation, it may not install.
Click to expand...
Click to collapse
Ok, how would I free up space on this partition, I take it you mean the phone rather than the SDcard ? I have most of my apps moved to the SDcard now, well the apps I can move anyway, some dont allow it.
I installed quick system info from market, it would appear out of the 250mb supplied I only have 70kb left, god knows where all this space has gone, but now im in catch 22, it would appear the reason I cant root is beacuse I dont have enough system space, but I cant delete any system apps cos im not rooted, any idea's anyone ?
Tried a reset of the phone but it didnt change anything in the system folder or available space.
Well, in layman's terms, the Desire has three user-visible partitions, excluding the SD card. Those are:
1) Data (/data): this is the partition where all your apps, app data, contacts and settings reside. This is also where the Dalvik-cache lives;
2) Cache (/cache): this partition is, as the name states, a cache partition;
3) System (/system): this is where your ROM resides. This is the partition where the .zip you're installing from Recovery is trying to copy its contents to, namely "Superuser.apk" and "su". In order for this procedure to succeed, you must have at least 900 kB free on this partition (Superuser.apk + su = ~860 kB, if you're trying to install Superuser 3.0.7).
If you're saying that you've checked the free space on your /system partition with a tool and it reports that you only have 70 kB free, that might be your problem. You can free up some space on the /system partition by deleting some files (which are safe to delete, namely some ringtones, a couple of wallpapers), but i must know what ROM are you using, first. Can you please provide that info?
P.S. - The above-mentioned procedure requires you to use ADB shell, so if you're not familiar with that or you just don't wanna mess with stuff like that, you can always install a pre-rooted ROM of your choice.
Hi, thanks for the info, it was very helpful, the ROM details are below, to me its just the stock Froyo ROM, but ive since unlocked the phone, S-OFF'd it and installed CWM, the HBOOT has also changed.
Andriod version 2.2
BB version: 32.48.00.32U_5.11.05.14
Kernal version: 2.6.32.15-ge2c73db
[email protected]#1
Build number: 2.22.351.3 CL283825 release-keys
Software number 2.22.351.3
Browser version Webkit 3.1
Hope this helps
I was also thinking of installing a pre-rooted ROM to get past this, As this would be my first time doing this I wasnt too sure which one to go for, the one I fancied is called PyramidMod007_v11_b-STOCK, would this go straight on ? the radio required is pretty much the same as my existing radio.
As mentioned earlier, I have a strange HBOOT version on my phone now, those details are as follows:
-Revolutionary-
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:10
HBOOT
(VOL UP ETC..............)
Nothing strange about your HBOOT. That's how it's supposed to "look" after using Revolutionary.
So you're running stock HTC FroYo. The way i see it, you shouldn't even bother rooting your current ROM, as FroYo is obsolete and you should move to Gingerbread. Browse through the development section, pick a ROM that you like and install it via Recovery (you don't need root for that). Mind you, you need to carefully read the requirements for each ROM. For example, some are made for the stock /system size (250 MB), some are made for the Data++ /system size (180 MB) etc. Also, some ROMs will not work without an EXT 3/4 partition on the SD card.
Thanks, I proceeded to try a couple of rom's out, tried the pyramid one first, but my phone was very very laggy with it, next I flashed the revolution rom, absolutly loving this rom, gonna stick with it for a bit I think, battery is much better on it, its nice as smooth, and boot times are amazing compared to the stock rom as well as now being rooted too.
I went for the apps2sd+ version of this rom, working fine on my current radio, I created a 1gb EXT3 partition on my SDcard prior to flashing using clockwork mod just incase, it said it required it.
Thanks for all your help guys, was so scared of bricking my phone through all of this, everything goes on about the risks all the time, but it was no where near as bad as that, guess they have to inform you though.
Well, the most dangerous procedures for your phone are when you're writing radios or HBOOTs. When you power up your phone, it first "boots" the Radio partition, then HBOOT and only afterwards it boots the kernel, OS etc. So if happen to frack up either one of these two partitions, Radio or HBOOT, you'll end up with a brick. Flashing ROMs or kernels, on the other hand, is perfectly safe.
Enjoy your "new" phone!
Have you tried unrevoked 3? It's work fine for me. I just ad to update superuser form the market after.
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
goxyendzy said:
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
Click to expand...
Click to collapse
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
nlooooo said:
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
Click to expand...
Click to collapse
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
goxyendzy said:
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
Click to expand...
Click to collapse
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
nlooooo said:
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
Click to expand...
Click to collapse
Thanks in advance, ill try everything when i setup everything properly. Will update on progress! :good:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
goxyendzy said:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
Click to expand...
Click to collapse
You have recovery, but it is stock one (pretty different to custom ones ).
Now after you flashed 2.3 RUU you probably have 1.02 hboot, so go here:
revolutionary.io
Download the tool and follow the process described to achieve s-off and root again (the problem you have have nothing connected with s-off and root but probably with some parts of system software which might be recovered now). During the process you will flash Clockworkmod recovery, from which you will install Superuser.apk. After that reboot the phone and go here:
4ext.net
Download Recovery updater, install it to your phone and flash 4ext recovery. Than from recovery you can restore backup you have from your old rom, but my suggestion is to go here:
http://forum.xda-developers.com/showthread.php?t=809328
and find something for you, cause I think that you have to start from scratch to have a proper software (cause you already had problems with previous one).
If you're up to Oxygen again go here:
http://download.oxygen.im/roms/
but I think that there are a few roms on previous link that are based on Oxygen, but a little bit modified with some extra options.
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
goxyendzy said:
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
Click to expand...
Click to collapse
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
nlooooo said:
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
Click to expand...
Click to collapse
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
goxyendzy said:
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
Click to expand...
Click to collapse
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
reboots again
nlooooo said:
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
Click to expand...
Click to collapse
Reboots again...
After half a day of normal usage, I tried inserting another SIM (but from same carrier) and it started again...
Not so often but from time to time it reboots.
So I guess, at the end it seems it is hardware fault.
One strange thing thou (and it makes me wonder): When I try removing account it says I should do Factory Reset if I want to change that basic acc. But afrer performing Factory Reset NOTHING happens? Account is still there, along with other settings and/or installed apps.
Any ideas?
Invitation still holds
I know, there are plenty of similar threads about this problem, but i found no one describing the same situation and offering good solution.
I rooted my HTC Desire Z about 3 months ago and since that i have been using ROM Virtuous Sense 2.0.0 without any troubles.
Yesterday, my phone was just lying on the table, while it suddenly restarted, i looked what happened and saw the HTC green logo on white background and then just black screen lasting for more then 10 minutes. I tried several times to to reset it by taking away the battery, but still the same. The most weird thing is, that it happened, while nobody was touching it and everything was ok. I can still go to the bootloader and to the Clockworkmod recovery, i tried wiping and formating the cash, but it didn't help.
Unfortunately i have no recent backups, so is there any way to fix it (at least temporarily, until i export contacts, app settings, etc) without wiping everything and installing the ROM again ?
If you require more info about hw/sw/status, just say.
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
demkantor said:
http://forum.xda-developers.com/showthread.php?p=33917375
Click to expand...
Click to collapse
1) I don't know much about android and rooting methods, i just found a website (http://wiki.cyanogenmod.org/wiki/HTC_Desire_Z:_Rooting) with a manual and i followed the steps without knowing what i was doing.
2) Yes, i can access both, and i can probably flash a new ROM, but i don't want until i know it is the only possible option
3) What i see on the main bootloader screen:
Code:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 8 2010,15:56:38
System info:
Code:
SN-SH192RT00257
LCD-SO
TOUCH PANEL-ATMELC12_20aaY
Commit-adbd7a75
OS Ver.-1.34.405.5
IMEI-352212049803773
CID-11111111
eMMC-samsung 2151MB 4407295sectors
Image crc:
Code:
hboot: 0x2A125CF4
boot: 0x16F3398
recovery: 0xB983BB96
system: 0xFC176473
4) ClockworkMod Recovery v5.0.2.7
5) This i described in previous post
6) /sbin/sh: logcat: not found
but i can access the phone with adb
when i try this cmd, the shell freezes without writing any output
cat /proc/kmsg | grep 'mmc0:0001'
but at first try it wrote this, before it froze
<6>[ 4.866851] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
output of cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name is
M4G2DE
note: wiping cash and dalvik cash didn't solve the problem, but i got stucked at the ROM logo instead of just black screen
It is looking as if you have a fried emmc and can not restore data or the phone no matter the method. If you are able to make a nanadroid (unlikely) you may be able to get some blob with your data but chances are phone is toast for good as well as any data on it
Sent from my HTC Vision using Tapatalk 2
I actually managed to do a full nandroid backup without any errors.
Would it be possible to wipe out and reinstall only the system partition and keep all user data unchanged ?
Not really, with a Linux box and some knowledge you can probably get you're info back then. But you'll have to ask someone else how I'm not good at understanding that language.
As for the phone you may be able to boot of SD card with the method catheral came up with, I believe I linked it in the other thread.
But of course just for sheer hope why not wipe and reinstall a new ROM. Occasionally the bad emmc seems to get a corrupt partition and a wipe/format will fix it.
then install a new ROM, know if this works it is only time before it goes bad again, possibly for good... its the nature of the chip
Or of course boot from SD, either way I suggest being on the lookout for a new phone as this one is either unrecoverable now or will be sometime (probably soon) at least you have the opportunity to get you're data back if you find someone with the knowledge
Sent from my Nexus 7 using xda premium
Looks like your prediction have come true.
After several unsuccessful attempts to recover system without removing user data, i did a full wipe and installed the ROM again. Then the phone booted successfully, but froze after few minutes, again and again.
Now it seems to be absolutely dead - power button does nothing and the LED doesn't light, when plugged to recharged. I guess it must be a hardware fault.
The phone is only 1 year and there is still warranty on it, so i have a good chance to return it to the shop, because since the chip is gone, they have little chance to discover that it was rooted and used other than stock ROM - am i right??
Anyway thanks for all the help
yup, and if i know you still had warranty i could have given you the super quick way of perma bricking your phone! but yeah, send it in now and see what the will offer you. if you can get another g2/dz id say take it as it is real hard to find a hardware qwerty to match. but of course choice is yours! good luck!
Hello all,
I realize that this is a common problem and that searching the forum SHOULD lead me to a viable solution, but alas this problem keeps rearing it's ugly head.
Ever since I initially rooted my phone, my phone will bootloop regardless of the ROM I flash to it. I am currently using the GBSense ROM.
In HBOOT, I am showing -
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-boot
I am using Revolutionary CWM v4.0.14
Any of this information provide clues to what could be causing my bootloop problem? Clearing the cache and Dalvik SOMETIMES works, but not always. Many times I am forced to do a factory reset, reload the image, restore from backup, and then pray that I don't lose battery or power down for any reason. :laugh:
Any help would be greatly appreciated.
Thanks!
You could always try using a different recovery. 4ext is a great option. As well as twrp. Twrp can be found in the development section. And the 4ext can be found by Google.
Sent from my Incredible 2 using Tapatalk 2
shniggens said:
Hello all,
I realize that this is a common problem and that searching the forum SHOULD lead me to a viable solution, but alas this problem keeps rearing it's ugly head.
Ever since I initially rooted my phone, my phone will bootloop regardless of the ROM I flash to it. I am currently using the GBSense ROM.
In HBOOT, I am showing -
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-boot
I am using Revolutionary CWM v4.0.14
Any of this information provide clues to what could be causing my bootloop problem? Clearing the cache and Dalvik SOMETIMES works, but not always. Many times I am forced to do a factory reset, reload the image, restore from backup, and then pray that I don't lose battery or power down for any reason. :laugh:
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
It's most likely the radio. Take a look at the radios thread in development and you will likely want the .0312 radio. Pay close attention to the instructions.
gtdtm said:
It's most likely the radio. Take a look at the radios thread in development and you will likely want the .0312 radio. Pay close attention to the instructions.
Click to expand...
Click to collapse
Well that appears to be the case! Thanks! I was on the verge of trying that, but I needed confirmation first. Once I changed the radio, it booted up no problem. Let's hope it stays that way!
shniggens said:
Well that appears to be the case! Thanks! I was on the verge of trying that, but I needed confirmation first. Once I changed the radio, it booted up no problem. Let's hope it stays that way!
Click to expand...
Click to collapse
No problem. Make sure to rename or move that file or every time you hit your bootloader you will be stuck in an endless loop where it tries to re-install that file.