Related
Created an Evo Splash Screen that everyone is welcome to use.
Put the file linked below into you're SDK/tools directory.
Reboot phone into bootloader.
Type "fastboot flash splash1 evosplash1.rgb565" (without the quotes) into the adb console.
Reboot and Enjoy.
Here's a link to the file you need:
http://www.megaupload.com/?d=QT6NU66C
Sun
Light
thanks its very nice
Thank you much sir! This is great
Can this be flashed with flash_image from the phone directly?
like this - flash_image splash1 filename ?
I believe it needs to be zipped and signed in order to be flashed.
I just read somewhere in google land that splash1 partition is called misc within android. I bet I'll brick it if I try to flash to misc. Or something...
When in the boot loader I can't get access to the device in adb shell. Any ideas?
eeeeeeeeek said:
When in the boot loader I can't get access to the device in adb shell. Any ideas?
Click to expand...
Click to collapse
1. Use adb to boot into the bootloader ">adb reboot bootloader"
*Once you're in bootloader adb commands don't work
2. Flash the .rgr565 file ">fastboot flash splash1 evosplash1.rgb565"
*Make sure the evosplash1.rgb565 file from the OP is in the SDK/tools directory on your PC
once in the boot loader it doesn't allow me to type anything, I can scroll between bootloader, reboot, reboot bootloader, and power down so I'm not sure if I understand step 2 of your response. Sorry Noobish on the evo, came from the samesung moment, thanks
eeeeeeeeek said:
When in the boot loader I can't get access to the device in adb shell. Any ideas?
Click to expand...
Click to collapse
I'm a noob too, but have had a little luck with ADB. Have you checked to make sure the USB Debugging in the Development menu is activated?
I have it on, I can use adb just fine when not in the bootloader, I'm just understanding how to flash from the boot loader.
Select fastboot from the bootloader. Connect your phone to the computer.
Your phone should say FASTBOOT USB near the top.
Now use a terminal and issue commands like you would with adb, only that the specific command is
Code:
fastboot flash splash1 evosplash1.rgb565
sweet that worked. Thanks!
Very nice. Like this a lot. Thank you
Created 2 more EVO splash screens for anyone to use if they wish:
Sun
Light
OP will be updated.
Jykinturah said:
Select fastboot from the bootloader. Connect your phone to the computer.
Your phone should say FASTBOOT USB near the top.
Now use a terminal and issue commands like you would with adb, only that the specific command is
Code:
fastboot flash splash1 evosplash1.rgb565
Click to expand...
Click to collapse
nevermind i got it
RickBaller said:
Created 2 more EVO splash screens for anyone to use if they wish:
Sun
Light
OP will be updated.
Click to expand...
Click to collapse
any chance you can whip up a version of light in red for my rom?
Yay 4 Juggs said:
any chance you can whip up a version of light in red for my rom?
Click to expand...
Click to collapse
Sure, post a screenshot and ill try and match it.
Yay 4 Juggs said:
any chance you can whip up a version of light in red for my rom?
Click to expand...
Click to collapse
Here you go bro.
http://www.megaupload.com/?d=H9ZGL7W7
ok so the rgb file we have to put it in the sd card directory right?
then either the sun or light file aswell?
Hey all -
So I followed instructions very specifically for rooting my Xoom on my Mac, and successfully unlocked the Xoom. As soon as I flashed the rootboot.img I rebooted and cannot get past the Motorola logo. I can get into Android Recovery, Fastboot and RSD protocall support but my Mac does not recognize it when I type in ./adb devices....what shall I do? I already performed Factory Reset but this didn't help.
P.S. When I say I followed instructions carefully, that is not to say this is anyone's fault but my own. I obviously did something wrong, and am realizing now that I flashed a 3.0 img file on my 3.1 Honeycomb...this is probably where I went wrong.
Any help would be greatly, greatly appreciated.
Thanks
I had a similar situation using rootboot, don't worry....download the proper boot.img from tiamat's thread, and flash it via fastboot the same way you did the previous one and reboot. That should fix you right up.
And your Xoom is nowhere near bricked, just a little confused. It will be alright.
Sent from my GT-I9000 using XDA Premium App
ah so quick! thank you thank you thank you. how do i flash it if the device won't show up though?
I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?
bloodmut said:
I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?
Click to expand...
Click to collapse
You said you could get into fastboot, yes? Power the Xoom down with power + volume up, reboot into fastboot with power + volume down, plug in the USB, open a prompt in the same folder as you have the new boot image and use the same command that you did before....should have been something like fastboot flash boot boot.img.
That is what worked for me in much the same situation.
Sent from my GT-I9000 using XDA Premium App
It keeps saying unable to create a plugin over and over and over
Ah ok wait. I needed to shut down Parallels. The command ran, but it said failed in terminal. On the Xoom, it says "Boot command is not allowed on consumer devices, Failed to process command error (0x8)"
bloodmut said:
It keeps saying unable to create a plugin over and over and over
Click to expand...
Click to collapse
Unable to create a plugin....hmmm..that one is new to me.
Still don;t panic. If there is a way to get into Fastboot then there is a way to install a new boot image.
Did you type adb remount to start out?
Just unlocked it again using ./fastboot-mac oem unlock...but when i type ./fastboot-mac boot boot.img it says the boot command is not allowed on consumer devices even though I unlocked it...also could you link the .img i'm supposed to use just so I can be sure lol
and no ./adb devices doesn't show my xoom
Here is the boot image...
http://forum.xda-developers.com/showthread.php?t=978013
and shouldn't the command be:
./fastboot-mac flash boot boot.img
Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!
bloodmut said:
Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!
Click to expand...
Click to collapse
No worries...I viewed it the same way. Down the line the knowledge you have been getting with this process will serve you well. Anyone can one-click, but doing it this way we learn how and why things work in Android.
Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch
Ended up flashing stock boot, system, and recovery images and am back to stock with no problems. Again, thank you for your patience and help.
bloodmut said:
Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch
Click to expand...
Click to collapse
Actually I would go in and flash Tiamat's kernel via CWM. That worked for me in restoring my wifi.
Otherwise you can run the following commands to restore wifi (I think...)
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
EDIT....OR you can just go back to stock and start again. Good luck.
Hi Trev here,I am a New member and hope this is posted in the correct place,I have a HTC ONE S S3 Version chip,No SD card version,has OPTUS AU Firmware on it with CID OPTUS_001,My system stopped booting when i tried to get Nova 3 game working,at the moment its not compatible for my device,but i read on the forums if i edited my Build prop I could get it working again,but sadly enough,it stopped booting the OS and i can sometimes get into the boot loader,Now the only way i can see to fix this is to get the original optus ruu and flash it but i cant find it any where,and i cannot install any of the other stock s3 roms because i don't have super CID,do you guys have any ideas,cheers Trev.
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
adb shell
qzem said:
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
Click to expand...
Click to collapse
Thanks for your reply,how do i change the build prop through adb shell,cheers.
build prop from one s s3 ruu
frdd said:
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
Click to expand...
Click to collapse
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
trevor3737 said:
Thanks for your reply,how do i change the build prop through adb shell,cheers.
Click to expand...
Click to collapse
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
trevor3737 said:
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
Click to expand...
Click to collapse
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
re build prop
frdd said:
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
Click to expand...
Click to collapse
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
trevor3737 said:
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
Click to expand...
Click to collapse
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
re adb pull
qzem said:
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
Click to expand...
Click to collapse
is where ever the place i send the build prop to,and when i run adb it say device not found,cheers.
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
re
frdd said:
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
Click to expand...
Click to collapse
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
trevor3737 said:
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
Click to expand...
Click to collapse
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
re recovery
frdd said:
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
Click to expand...
Click to collapse
I have uploaded a pic of the boot loader,i have root access via pauls super boot,boot loader is unlocked and i know how to re lock if i have to ,cheers.
trevor3737 said:
When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers
Click to expand...
Click to collapse
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
re recovery
[/ATTACH]
frdd said:
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
Click to expand...
Click to collapse
thats what happens when i hit recovery from the bootloader screen.
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
re flash recovery
qzem said:
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
Click to expand...
Click to collapse
it says remote not allowed
re
trevor3737 said:
it says remote not allowed
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.188s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.188s
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
re flash recovery
frdd said:
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.172s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.188s
C:\Android>fastboot flash recovery recovery-signed.img
error: cannot load 'recovery-signed.img'
the fastboot boot recovery_signed.img way and the fastboot flash recovery recovery-signed.img way
what is the standard procedure on changing the recovery? i have CWM on it right now. not sure on how to remove that and then install the smelkus one. found a video on yt saying to use terminal emulator to flash it, it "flashed it" but now it just goes to the bootloader menu where you choose fastboot or the other option. still boots into the OS fine tho
douellette said:
what is the standard procedure on changing the recovery? i have CWM on it right now. not sure on how to remove that and then install the smelkus one. found a video on yt saying to use terminal emulator to flash it, it "flashed it" but now it just goes to the bootloader menu where you choose fastboot or the other option. still boots into the OS fine tho
Click to expand...
Click to collapse
Try flashing it via fastboot.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Theonew said:
Try flashing it via fastboot.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
how do i do that? terminal emulator? do i type anything else or just that and then reboot into recovery from the desktop?
douellette said:
how do i do that? terminal emulator? do i type anything else or just that and then reboot into recovery from the desktop?
Click to expand...
Click to collapse
No. You run those commands from your PC.
finally got it, opened rom manger and it had the option right in there to flash smelkus. so its all set, thanks!
douellette said:
finally got it, opened rom manger and it had the option right in there to flash smelkus. so its all set, thanks!
Click to expand...
Click to collapse
I guess that's the simpler way .
NB/EDIT : I am pretty sure this is due to cmupdater requiring "next boot" to recovery. Is there any way to get through this?
NB/ EDIT : Now, I can cold boot. But the flash (DD/ fastboot seems not be working. hope better news next hours).
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...
http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
florck said:
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...
Click to expand...
Click to collapse
Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
elfaure said:
http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
Click to expand...
Click to collapse
florck said:
Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
Click to expand...
Click to collapse
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com
elfaure said:
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com
Click to expand...
Click to collapse
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
florck said:
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
Click to expand...
Click to collapse
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
_that said:
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
Click to expand...
Click to collapse
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
florck said:
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
Click to expand...
Click to collapse
Why doesn't adb work? Can you see any USB device on your computer?
_that said:
Why doesn't adb work? Can you see any USB device on your computer?
Click to expand...
Click to collapse
Oh ! I got and ADB shell.
but when I "ls /dev/block", I only get
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p3
platform
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?
florck said:
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?
Click to expand...
Click to collapse
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment bootit.zip
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.
_that said:
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment 1985914
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.
Click to expand...
Click to collapse
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?
florck said:
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?
Click to expand...
Click to collapse
The funny serial number is normal for the recovery.
Try the procedure again and hold down volume-left immediately after pressing "Enter" in adb shell on the insmod command. Maybe you can get to the bootloader menu. If not, I'll try to build another kernel module.
That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
florck said:
That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
Click to expand...
Click to collapse
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment bootit-bootloader.zip
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
_that said:
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment 1985941
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
Click to expand...
Click to collapse
You're a genius, I can now fastboot and / or cold boot. When I cold boot I have my fully functional previous android. But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?
florck said:
You're a genius, I can now fastboot and / or cold boot.
Click to expand...
Click to collapse
That's good news - until today your situation was considered an unrecoverable hard brick.
florck said:
But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?
Click to expand...
Click to collapse
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...
florck said:
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...
Click to expand...
Click to collapse
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461
_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
_that said:
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461
Click to expand...
Click to collapse
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...
florck said:
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...
Click to expand...
Click to collapse
Any other idea ? Something to flash in other blocks?