This is what happend to me and many other people: HTC Desire S - Bad eMMC
I still have 3 months warranty and dont want HTC to have an excuse to void my warranty and make me pay for a replacement Mainboard.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems the eMMc was not fried by me or the s-off tool, but HTC just cheaped out on the eMMC chips in these phones.
Does anybody got tips on how to brick a phone, oh yeah blender, microwave/sledgehammer/ex-wife, would destroy it, and I'm just trying to brick it, no physical damage.
Looking for a warranty replacement. If your not comfortable with writing this down here, than pm me please.
Hit your phone with a sledgehammer.
Or just keep pulling the battery out when doing almost anything on the phone.
Throw over the wall but gantly
It is possible. There is a dd command you can run that will totaly brick it.
But you should have no issues getting your device repaired despite being rooted and s-off. HTC are aware of the emmc issue and I know of lots of people with HTC vision's who have had no issues getting a replacement.
But if you really want to brick it I know who to ask for the cmd.
I will pm you if I get it
Sent from my HTC Desire S using Tapatalk
Pull battery while flashing a ROM
djpbx said:
Pull battery while flashing a ROM
Click to expand...
Click to collapse
He can't flash a rom. And pulling the battery when flashing a rom is unadvised but is unlikely to brick you're phone. You recovery and bootloader partitions are unaffected by when you flash a rom. So you would still be able to access them and recover from pulling the battery during the flash
Sent from my HTC Desire S using Tapatalk
Also, it is in some situations possible to recover from a bad EMMC. Sometimes it can just be that your partition table is messed up. And can be fixed.
@OP I'm guessing you can get into recovery, but the "error can't mount cache" etc warnings?
Sent from my HTC Vision using Tapatalk
I just sent in the phone without the battery and sd card and got a repaired phone. Can't guarantee the same luck though
Sent from my HTC Desire S using xda premium
cjward23 said:
Also, it is in some situations possible to recover from a bad EMMC. Sometimes it can just be that your partition table is messed up. And can be fixed.
@OP I'm guessing you can get into recovery, but the "error can't mount cache" etc warnings?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
================what happend================
While updating some apps from the market, DS freezes longer then 2 hours.
I pulled out battery and reboot, and there came loopboot.
got in Recovery, it promts
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
================things i did================
1. [ wipe data/factory reset]
Code:
Formating /data...
black splash screen, and then
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
[ wipe cache ]
Code:
Formating /cache...
Cache wipe complete.
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
2. [ install zip from sdcard ]
Code:
-Checking Model ID
-success!
-Model ID - HTC sage
Now flashing
E:Error in /sdcard/*******.zip
(Status 1)
Installation aborted.
3. [ backup and restore ]
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoreing system....
Error while formatting /system!
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
4. [ RUU+Goldencard ]
Goldencard is good, in FASTBOOT USB mod,
passed the (version) checking, updating 1.28.401.1 to 1.47.950.3, but stuck at
Code:
rebooting bootloader ......
upgrading ROM image in your Android Phone...
Please do NOT disconnect USB cable nor run any program.
5. [ ROM.zip->PG88IMG.zip ]
ROM.zip was picked-up from RUU, renamed to PG88IMG.zip, copied to sdcard,
reboot to HBOOT, and it unzip the pack normally, then stuck at updating screen, more than 1 hour.
Code:
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] BOOTLOADER -updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SLPASH1
[6] USERDATA
[7] TP
[8] DADIO_V2
[9] RADIO_CUST
Do you want to start update?
[/INDENT]
6. [ PG88IMG.zip for Recovery/Radio ]
HBOOT asks do you wanna upgrade, click VOL-up, then stuck at updating screen
Code:
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] RECOVERY -updating
*********
Updating is in progress...
Do not power off the device!
[/INDENT]
7. [ fastboot ]
Code:
SH********8 Connected.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 38.03.02.15_m.
SPL/hboot version: 0.98.0000.
product: saga.
mid: pg88*****.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
[B]fastboot erase cache[/B]
erasing 'cache'...
[COLOR=red]erasing 'cache'... FAILED (command write failed (Unknown error))[/COLOR]
I have just shown this thread to the guys in #G2ROOT. These guys have more experience of fried EMMC's than anyone else.
I'm afraid there is nothing that can be done to fix your device or brick it any more than it all ready is.
Lots of people have had it repaired despite being s-off.
You just need to send it off and hope for the best
Sent from my HTC Vision using Tapatalk
cjward23 said:
Lots of people have had it repaired despite being s-off.
Click to expand...
Click to collapse
I afraid that 95% of the stories from people with HBOOT-6.98.1002 are saying something else...
spankranger said:
I afraid that 95% of the stories from people with HBOOT-6.98.1002 are saying something else...
Click to expand...
Click to collapse
I can only relate to the issues I have encountered with the HTC Vision.
I'm one of them I had an EMMC fail. And got a warranty replacement, no questions asked.
Sent from my HTC Vision using Tapatalk
cjward23 said:
I can only relate to the issues I have encountered with the HTC Vision.
I'm one of them I had an EMMC fail. And got a warranty replacement, no questions asked.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Just got a message from HTC Netherlands after sending my phone to them.
They say that the eMMc was fried by the s-off tool I had used. And thats why my warranty is now void. They tell me the replacement of the main board cost me €180,-
But if i dont want that and just want to get my phone back, i still need to pay them €30,- for the research of it. WTF!! next time i will microwave the freaking phone before i sent it to them. Now they just refurbish it and give it away....
I'm totaly done with this policy. thanks again for everybody's help.
cjward23 said:
I have just shown this thread to the guys in #G2ROOT. These guys have more experience of fried EMMC's than anyone else.
I'm afraid there is nothing that can be done to fix your device or brick it any more than it all ready is.
Lots of people have had it repaired despite being s-off.
You just need to send it off and hope for the best
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Pretty much sums the situation up. HTC are aware but suspect this will also depend on the repair tech some may just see the s-off and disclaim the warranty.
Even if the phone screen etc does not display the USB will probably still allow adb shell
Sent from my HTC Desire
Related
I know this the wrong forum but I need developers help my camera app keeps fc and says report to Google
Sent from my Nexus S using XDA App
can you be more specific?
custom rom, kernel or what have you
2.3 1, I902XXJK8, Kernal 2.6.35.7-g7f1638a, [email protected]#1
Sent from my Nexus S using XDA App
your running gingerbread yes, but who made the rom?
(cyanogen,modaco,etc)
or is it stock??
Its stock I'm not even rooted everything works but the camera
Sent from my Nexus S using XDA App
Thats strange dont know y ur camera would stop working running stock. Might be a software issue so u may wanna take it back an exchange it
The application camera (process com.Google.android camera) has stopped unexpectedly please try again
That's what it keeps saying
Sent from my Nexus S using XDA App
go to main settings, applications, manage applications, all, camera, clear data. then you should reboot.
I did that almost a hundred times
Sent from my Nexus S using XDA App
Bspence415 said:
I did that almost a hundred times
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
try moving all your camera pictures to your desktop. then clear your data in the camera app and the gallery app. you might have to factory reset to fix it, so consider backing up some of your data.
Bspence415 said:
I did that almost a hundred times
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
have you considered unlocking your bootloader(rooting your phone)?
That's what I'm going to try tonight is there a one click root like for the galaxy because I don't know how to root sns yet
Sent from my Nexus S using XDA App
Bspence415 said:
That's what I'm going to try tonight is there a one click root like for the galaxy because I don't know how to root sns yet
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
very easy, you dont need an app for it. very basically... install drivers to your desktop, download sdk, "fastboot oem unlock", flash clockwork recovery, flash a rom(and gapps if needed). read the threads here. shouldnt take you more than 30-60min.
How do I do the fastboot OEM unlock?
Sent from my Nexus S using XDA App
Bspence415 said:
How do I do the fastboot OEM unlock?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
taken from this thread... http://forum.xda-developers.com/showthread.php?p=10238318#post10238318
AllGamer said:
GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
Part 1
Download Android SDK 2.3 or click the file name android-sdk_r08-windows.zip (32 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK 2.3 (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!
Click to expand...
Click to collapse
Seriously, you have a buggy phone before even rooting, I'm not sure rooting will fix it for you. What if your hardware for the camera is bad and that's what's causing the problem? Once rooted, you'll have to worry about un-rooting and relocking the bootloader to avoid any warranty hassles. I'd take it back and exchange it before rooting.
Make sure you have a solid working phone before rooting!
On another note, even though it's in red in the posted tutorial, let me reemphasize that the oem unlock step WILL WIPE EVERYTHING ON YOUR PHONE, INCLUDING THE SDCARD (internal one)...so if you have any pics or stuff on there you can't afford to lose, transfer them to the computer via USB before starting the root process.
CWM is finally here on I9003 for XXKPE
HOW TO:
- Install the latest CWM with EXT4 support;
- do a full backup with nandroid;
- install the attached script (DO NOT REBOOT AFTER THIS STEP);
- restore backup.
IMPORTANT: Read this topic on Edify scripting used on update.zip. The partitions must be mounted before copying files:
Code:
run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/stl9", "/system");
Flashing Zip Files:
If in the updater-script there isn't the "mount /system" option you must - before apply the zip - mount manually /system under "Mount and Storage" menu and then flash your zip.
Feature:
- Added EXT4 filesystem support for the kernel;
- CWM with double RFS / EXT4 filesystem support;
- Busybox;
- Juwe11's RamScript from http://forum.xda-developers.com/showthread.php?t=1111145 ;
THANKS:
A big Thanks to the Skin1980 (this CWM is heavily based on it's project).
Thanks also to koush that made the Clockworkmode Recovery.
Attached you will find the CWM for each FW... just flash with ODIN selecting in the PDA source the CWM file.
UPDATE: 08/02/2011 Added the support for Juwe11's RamScript
Just press "Thanks" if you like my work...!!!
So this is it! Thanks X 2 mate! I'm installing the converter immediately
@OP: Thanks, does this support init.d script, so I can use a script like juwe's ram script?
Root issue!
The same as Skin's first version of ext4 converter :
The installation was completed, but when I come back to CWM main menu, recovery writes :
E:Can't mount /cache/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I reboot, it's stucking to the boot screen ("Galaxy S Super Clean LCD")
@pralinos: at work now, can't try it, but did you mean it got stuck at boot screen after you tried to root or even before it? I haven't root my phone and only want to do an ext4 conversion.
Pralinos said:
The same as Skin's first version of ext4 converter :
The installation was completed, but when I come back to CWM main menu, recovery writes :
E:Can't mount /cache/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I reboot, it's stucking to the boot screen ("Galaxy S Super Clean LCD")
Click to expand...
Click to collapse
After the third step (in the instructions), do not reboot the phone.
Updated the instructions for the same.
Let me know how it goes.
bigeyes0x0 said:
@pralinos: at work now, can't try it, but did you mean it got stuck at boot screen after you tried to root or even before it? I haven't root my phone and only want to do an ext4 conversion.
Click to expand...
Click to collapse
My phone was rooted before I applyed the ext4-format.zip. You need root access to use CWM.
amit.bagaria said:
After the third step (in the instructions), do not reboot the phone.
Updated the instructions for the same.
Let me know how it goes.
Click to expand...
Click to collapse
It doesn't work :
Checking MD sums...
Restoring system...
Error mounting /system
Skipping format...
Can't open /system
I think I lost root access just after I applyed the zip, because the error messages appeared as soon as I came back to CWM main menu.
@amit, I have just flashed XXKPE with CWM as per these posts, http://forum.xda-developers.com/show...6#post16169086 and http://forum.xda-developers.com/show...&postcount=537.
Now if I want to convert to Ext4 (Internal memory or internal SD card or both??), I believe I have to flash the files in this thread? Will I lost all my apps and data?
Amit, the same happened to Skin when he first released ext-format.zip for Froyo.
See http://forum.xda-developers.com/showthread.php?t=1151704&page=53
You musn't be far from succeeding.
Pralinos said:
Amit, the same happened to Skin when he first released ext-format.zip for Froyo.
See http://forum.xda-developers.com/showthread.php?t=1151704&page=53
You musn't be far from succeeding.
Click to expand...
Click to collapse
There is nothing wrong in the version I posted. Basically if you have rebooted the phone after running ext4 conversion update script, then it won't work. You would need to reflash the vanilla XXKBE and then perform the steps listed in the instruction (Obviously skipping the 2nd step, since I assume, you would have already done nandroid backup )
@amit: how high did the i/o quadrant scored? Gonna try this later
Sent from my GT-I9003 using XDA Premium App
ok i copied the ext4-format.zip in my sdcard n booted to cwm recovery
now i select install zip from sdcard>choose zip from sdcard.but i cant see the ext4-format.zip.
am i doing something wrong.would appreciate a more detailed explanation on what to do.
jit_devil2 said:
ok i copied the ext4-format.zip in my sdcard n booted to cwm recovery
now i select install zip from sdcard>choose zip from sdcard.but i cant see the ext4-format.zip.
am i doing something wrong.would appreciate a more detailed explanation on what to do.
Click to expand...
Click to collapse
For CWM sdcard = External SD Card
Copy again to external SD card and give it a shot
whats this ext4-format?
Quadrant Scores
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
amit.bagaria said:
Click to expand...
Click to collapse
Great.! Do u have advanced quadrant? It's more detailed
Sent from my GT-I9003 using XDA Premium App
@amit... how to check above ss & whats d ext4 support?
soodgautam said:
For CWM sdcard = External SD Card
Copy again to external SD card and give it a shot
Click to expand...
Click to collapse
thnks trying it now
it works perfectly 2156 in quadrant.
awesome work.now waiting for ram script
I tried to S-Off my Desire S using the revolutionary tool and followed instructions. Towards the end of the process and revolutionary tool stopped responding and it forced me to end the application. Tried checking if it went successful, it said that my phone was on S-Off. I tried going to recovery and flash "this zipfile" (source: http://unrevoked.com/rootwiki/doku.p.../revolutionary) to root the device since gingerbreak was not working. I got the icon of a phone with red triangle and exclamation point. I did do volume up key + power to enter to recovery then i got the error E:Can't open /cache/recovery/command
Please help.
phone info:
Kernel Version - 2.6.35.10-g2ee27f5
software number - 1.48.707.1
hboot version - 0.98.0002
You must search and read the forum
Possibly bad news see this thread http://forum.xda-developers.com/showthread.php?t=1242031 which I only answered yesterday http://forum.xda-developers.com/showthread.php?t=1239949
Swyped from HTC Desire S using XDA Premium
Posted in error
thanks for the reply. i actually read that but i thought it would be different from what i experienced. anyway, should i try to wipe the cache and try to see if it works?
boazgalpo said:
thanks for the reply. i actually read that but i thought it would be different from what i experienced. anyway, should i try to wipe the cache and try to see if it works?
Click to expand...
Click to collapse
Yes, wipe the cache. You will not lose anything either way.
If it does not work? It's safe to say that what ben_pyett said is most probably true? "fried eMMC Chip"
boazgalpo said:
If it does not work? It's safe to say that what ben_pyett said is most probably true? "fried eMMC Chip"
Click to expand...
Click to collapse
I don't know a lot about the issue, but from what I have read on the forum, that would be the likely situation.
djsubtronic said:
I don't know a lot about the issue, but from what I have read on the forum, that would be the likely situation.
Click to expand...
Click to collapse
that would suck big time. other than that, there would be no issue if won't try to root my phone right?
boazgalpo said:
that would suck big time. other than that, there would be no issue if won't try to root my phone right?
Click to expand...
Click to collapse
Not true people have hit this problem after performing a factory reset of the device and during the market re-install of their applications.
Others have hit this problem after pulling battery after device crash, the cause of crash can be a multitude of things, from a hung third party downloaded application to re-install or flash of a new ROM.
Just always take backups and try to be careful. Only do what you fully understand.
If device crashes always try Volume up key + Volume Down Key + Power key to reset before resorting to battery pull. Plus remember that the battery should never be pulled and re-inserted too quickly.
@ben_pyett thank you so much for your help. What would you suggest that I do now? I already tried wipe the cache, it just says wipe successful. the options i have after is to reboot system and install update from sdcard? do i need to download something like CWD recovery? If yes, where can I download that? Thanks. I apologize for the ignorance.
boazgalpo said:
@ben_pyett thank you so much for your help. What would you suggest that I do now? I already tried wipe the cache, it just says wipe successful. the options i have after is to reboot system and install update from sdcard? do i need to download something like CWD recovery? If yes, where can I download that? Thanks. I apologize for the ignorance.
Click to expand...
Click to collapse
No problem, this appears to be happening very frequency to people, so I think we need to do more tests before we say fried chip.
In my signature is a link fried emmc? Try to do some off the commands In this as this will determine whether you have a bad chip, you'll also find the link to fast boot and adb commands that you need on the pc in order to run these commands in my signature
I'll look back tomorrow and we can try again
No need to apologise we are all learning here, I'll provide instructions in how to install EXT4 recovery next tune I'm at a PC, in the morning
Swyped from HTC Desire S using XDA Premium
I faced same with revolutionary. After it says s off, I used super1click which successfully rooted my phone HTC desire s
where do I download super1click? thanks for the help sagarda7
sagarda7 said:
I faced same with revolutionary. After it says s off, I used super1click which successfully rooted my phone HTC desire s
Click to expand...
Click to collapse
@sagarda7
Funnily enough, superoneclick is what I used many months back to root my phone in the days when GingerBreak didn't work for our device.
@boazgalpo
Although, initially something that I'd like you to try is to attempt to install the EXT4 custom recovery onto your device:
1) download and unzip this file on to your PC.
2) Plug your booted device into the computer using USB (with debugging enabled)
3) Run a Command Prompt window on the PC where the unzipped files are accessible run the script called runme.cmd (cut n paste the screen output)
4) Boot into recovery to see if it worked?
EDIT:
You download superoneclick from here, it has its own site although give my suggestion a go first.
As if it works you'll be able to simply flash a custom ROM which will come rooted.
Thanks a lot man. I will surely try that.
pushing files with adb..
..
338 KB/s (92632 bytes in 0.267s)
402 KB/s (6572032 bytes in 15.948s)
..
..
writing recovery..
su: permission denied
..
removing leftover files..
finished
No Errors? Then it should have worked.. reboot into recovery to check
Press any key to continue . . .
this is the screen output...
EDIT: tried going to recovery to check, still got the icon of the phone with red triangle
tried superoneclick v.2.1.1 as well. got stuck at step #6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Help please...
Sent from my Desire HD using xda premium
@ben_pyett
hi, would it help if i try to hard reset my phone first then try to do the instructions you gave me or it wouldn't really matter? thanks
i did hard reset the phone and did 4ext recovery but it didn't seem to work still. here's the screen output
pushing files with adb..
..
adb server is out of date. killing...
* daemon started successfully *
395 KB/s (92632 bytes in 0.229s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
400 KB/s (6572032 bytes in 16.009s)
..
..
writing recovery..
adb server is out of date. killing...
* daemon started successfully *
su: permission denied
..
removing leftover files..
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
finished
No Errors? Then it should have worked.. reboot into recovery to check
Press any key to continue . . .
Click to expand...
Click to collapse
help help help!
I am having so much trouble getting mytouch4gS to root. I am under the impression that the usb drivers aren't installed Though I could be wrong... I've downloaded HTC Sync (It doesn't recognize the device) Installed with anti-virus disabled, Fastboot is off, USB debug enabled. I've tried using the HTC Boot Unlocker, Revolutionary Method, and one of the Tool Kits here on XDA and none seem to be able to recognize my device... How the fok do I get this thing rooted?
HBOOT: 1.44.0007 (S-On)
This is the code that it throws
Code:
C:\Users\Admin>cd \Android
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
Go with Revolutionary. I had problems initially getting the token to work but I was substituting a zero for an "O" or something. I copied and pasted the token from Revolutionary and it worked like a champ.
Sent from my RubiX CubeD Extreme MT4GS using Tapatalk
Coug76 said:
Go with Revolutionary. I had problems initially getting the token to work but I was substituting a zero for an "O" or something. I copied and pasted the token from Revolutionary and it worked like a champ.
Sent from my RubiX CubeD Extreme MT4GS using Tapatalk
Click to expand...
Click to collapse
When I run Revolutionary nothing happens. The cmd prompt pops up then disappears immediately. I dont even get a chance to put in anything
run Mr Root...it'll work for sure
xmc wildchild22 said:
run Mr Root...it'll work for sure
Click to expand...
Click to collapse
I'm running 32 bit W7 Home Premium and it says The version of this file is not compatible with the version of Windows you are running....
My laptop runs Ubuntu, if anyone knows of a Linux based root?
Maybe the download link was corrupt or something, I'll try the 4shared mirror
Did you install the fastboot drivers?
They are seperate from htc sync.
You can find them on the revolutionary page.
Use rev to s-off it and then you can root your rom or install a new one after replacing your recovery.
Sent from my Bulletproof_Doubleshot using xda premium
Blue6IX said:
Did you install the fastboot drivers?
They are seperate from htc sync.
You can find them on the revolutionary page.
Use rev to s-off it and then you can root your rom or install a new one after replacing your recovery.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
Thank you! Much Love & Respect
it should work...what happened when you clicked on it?
Keep getting invalid beta key? How do I paste into Revolutionary?
EDIT/SOLUTION: Betakey is strange... Paste into word pad and type out characters until they match exactly using a different font before entering key
xmc wildchild22 said:
it should work...what happened when you clicked on it?
Click to expand...
Click to collapse
This
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hmm kk thank you
Fully Rooted. S-Off.
Attached is Fastboot.exe from Mr. Root and Signed Superuser.
This is the step by step I used for revolutionary for anyone in the future who is having issues with rooting their MyTouch 4g Slide /Doubleshot
http://theunlockr.com/2011/09/09/how-to-permanently-root-and-gain-s-off-on-the-t-mobile-mytouch-4g-slide-revolutionary-method/
II. Gain S-Off
1. Download the latest version of the tool from the developers here (the initial versions require you to generate a beta key for you to use the program, just follow the steps to do so. If it lets you download the program without a beta key, then it’s a newer version than at the time of writing this, just continue):
Revolutionary
2. Plug in your device.
3. Select charge only if the option exists on your device, or just do NOT mount the SD Card.
4. On your device, click on Settings > Applications > Development > Turn USB Debugging ON.
5. Find the Revolutionary program you downloaded and unzip it to the TempRoot folder inside the TempRoot folder you extracted in Section II.
6. Right click it and select Open as Administrator (if you do not have that option when you right click, simply select Open).
7. Input your beta key you received and wait for it to do it’s thing (if you are using a newer version of Revolutionary then it might not ask you for this. If that is the case, just continue).
III. Flash a Custom Recovery Image
1.. Once done gaining S-Off, it will ask you if you want to flash clockworkmod recovery, type in y and hit enter.
2. Once it is done flashing the recovery image it will close the command prompt window.
3. On your phone, you should see S-Off at the top.
4. Take out the battery and put it back in.
5. Turn on the device, by holding down volume down and power until the screen boots up.
6. Push volume down and then power to select recovery.
7. If the phone reboots to the clockworkmod recovery screen you are all set.
IV. Gain Permanent Root Access.
1. With the phone still in clockworkmod recovery from the last step, plug it in via USB cable.
2. Select Mounts and Storage by using the volume buttons to move and power to select.
3. Then select mount USB storage (the sd card directory should pop up on your computer screen)
4. Download the root .zip file and save it to your computer (do NOT extract it)
MyTouch Slide 4G Root .zip File
5. Copy the root .zip file to the root of your sdcard and wait for it to transfer (not in any folders, just on the sd card itself).
6. On your device, select unmount sdcard.
7. On your device, select go back.
8. Then select Install zip from sdcard and choose the root .zip file.
9. Wait for it to flash, once done, select reboot system now.
10. Once your device reboots, open the app drawer and you should see Superuser permissions there. If so, you are all set, you are rooted, have S-Off and a custom recovery image.
optimus x said:
This
Click to expand...
Click to collapse
I am getting the same error.
^ I also get the same error
Are you on 32 bit Windows?
xmc wildchild22 said:
Are you on 32 bit Windows?
Click to expand...
Click to collapse
Yes I am
Sent from my SGH-T959V using XDA
Yes, i'm also on 32 bit
Hi
The best way I found was here:
http://wiki.rootzwiki.com/HTC_myTouch_4G_Slide
It does have the Revolutionary Method, but for some reason, I found these directions easiest to follow.
Good luck.
Deleted
Flacito13 said:
I think I bricked my Poco F2 Pro (Redmi K30 Pro). I installed LuckyPatcher to disable disable signature verification. When I LuckyPatcher rebooted, I got stuck in a bootloop (the phone booted to Fastboot instead of System). I now want to format data in my TWRP to flash a new ROM and start from scratch. However, when I format data I get the following error in my TWRP: Failed to mount 'system_root' (Read-only file system).
I tried unsuccessfully tried fixing it by starting Terminal in TWRP and typing "mount -o rw,remount /system". I get "mount: can't find /system in /etc/fstab. with "mount -s system", I get a bunch of text but nothing that makes sense to me.
I hope somebody can help me out here...I just bought it :crying:
Click to expand...
Click to collapse
I have the same issue. Just install fresh rom with xiaomi tool and everything should be fine.
Koziol87 said:
I have the same issue. Just install fresh rom with xiaomi tool and everything should be fine.
Click to expand...
Click to collapse
I successfully flashed, but I still get "failed to mount /system_root (read-only file system)"...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Flacito13 said:
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Click to expand...
Click to collapse
have you tried with XiaomiTools?
Flacito13 said:
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Click to expand...
Click to collapse
Did You flash 4 part file?
Koziol87 said:
Did You flash 4 part file?
Click to expand...
Click to collapse
What is 4 part file?
kevinmonja said:
have you tried with XiaomiTools?
Click to expand...
Click to collapse
I tried, but I get this error:
Flacito13 said:
I tried, but I get this error:
Click to expand...
Click to collapse
what rom are you trying to flash?
What TWRP version did you install? I recommend 3.4.2B from LR.Team.
batuken said:
What TWRP version did you install? I recommend 3.4.2B from LR.Team.
Click to expand...
Click to collapse
I have it...the problem is still that the system_root is "read-only"...:crying::crying::crying:
EDIT: after flashing with the xiaomitool, I now get error when formating data: failed to mount /odm invalid argument
kevinmonja said:
what rom are you trying to flash?
Click to expand...
Click to collapse
The one automatically downloaded by the flash tool. It is: lmi_eea_global_images_V12.0.2.0.QJKEUXM_20200730.0000.00_10.0_eea_7a4654b9f8
I tried formatting data again, but now I get another error: "failed to mount /odm invalid argument"
Flacito13 said:
The one automatically downloaded by the flash tool. It is: lmi_eea_global_images_V12.0.2.0.QJKEUXM_20200730.0000.00_10.0_eea_7a4654b9f8
I tried formatting data again, but now I get another error: "failed to mount /odm invalid argument"
Click to expand...
Click to collapse
Try to flash Xiaomi.eu ROM in TWRP.
batuken said:
Try to flash Xiaomi.eu ROM in TWRP.
Click to expand...
Click to collapse
failed to mount '/odm' (invalid argument)
Flacito13 said:
failed to mount '/odm' (invalid argument)
Click to expand...
Click to collapse
I had this problem a few days ago. To solve it, I had to reflash the rom (without formatting any partition) from twrp, ignoring the errors. (I'm on xiaomi.eu stable rom)
The important thing is to never modify the system partition (via lucky patcher or other tool) after installing Magisk, otherwise the phone won't reboot.
Lowxorx said:
I had this problem a few days ago. To solve it, I had to reflash the rom (without formatting any partition) from twrp, ignoring the errors. (I'm on xiaomi.eu stable rom)
The important thing is to never modify the system partition (via lucky patcher or other tool) after installing Magisk, otherwise the phone won't reboot.
Click to expand...
Click to collapse
Look the picture, I reflashed the rom with twrp. I still get the error cannot mount.
I see that some people have solved it by external rom installation, using adb sideload? How do I do that?
Deleted
Flacito13 said:
Look the picture, I reflashed the rom with twrp. I still get the error cannot mount.
I see that some people have solved it by external rom installation, using adb sideload? How do I do that?
Click to expand...
Click to collapse
I tried flashing via adb sideload in twrp, my devices wasnt recognized. Had to use my OTG USB Flashdrive.
ok i try side loading
I had same problem and go to twrp,format data type YES then reboot to twrp and clean cache,data,dalvik,interal,not wipe system...and reboot to twrp,put stable rom from xiaoimi.eu and flash it