Hi...
I am using a Milestone XT720 now, and had rooted my handheld.
Would appreciate to have any tutorial how to have the Apps2SD work on my XT720, please.
Thank you.
Rgds,
Andika
i have been trying different apps which work on nexus one. it doesn't seem to work on the xt720.
I successfully did it on Motoroi Xt720. i just use the rom manager to partition my sd card
But the rom have to be prepared to app2sd, isnt true?
Sent from my Milestone XT720
I just copied this to other forum i forgot cause i've saved this as txt file. credits to this are for the owner.
1. App2SD Version 2 (Download the attachment)
This revised version of App2SD is more refine. It moves cache as well as apps to MicroSD.
Steps to prepare for installation:
1. Unzip the downloaded file and you should see a folder "APP2SD Package".
2. Rename "APP2SD Package" folder to "app2sd" and move this folder to MicroSD. (place it in the root: MicroSD card/)
Next, simply connect the Milestone to your computer.
Ensure it is "Charge Only" for USB connection and USB Debugging mode for USB is turned on under Settings > Applications > Development.
Once you have the above checked, go ahead to launch a command prompt and perform the following:
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
I did this on my Motoroi XT720 I dont know in the other model, but i think it will work.
not successful.
first of all, you need to create ext2 partition on your SD card.
but even i got ext2 partition,
i got this error "mount: block device required"
I suggest you use the rom manager's "partition sdcard"
Sent from my XT720 using Tapatalk
jakelights said:
I suggest you use the rom manager's "partition sdcard"
Sent from my XT720 using Tapatalk
Click to expand...
Click to collapse
You mentioned that you are using rom manager to partition the sd card. have you tried installing the clockworks recovery mod thru it? the drop down menu in the app shows motorola milestone but not sure if it will work for XT720.
bu2askoor said:
You mentioned that you are using rom manager to partition the sd card. have you tried installing the clockworks recovery mod thru it? the drop down menu in the app shows motorola milestone but not sure if it will work for XT720.
Click to expand...
Click to collapse
same thing here ..............i cant find XT720 .....................
Got It To Work!!
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
yadvani said:
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
Click to expand...
Click to collapse
hi thanks for the steps, just to confirm a few things:
1) i think we don't need the swap partition right? swap partition is used for linux swap which only custom kernel can use right?
2) is there a way to reverse app2sd later? i am asking because i believe the froyo is near. will we have problem upgrading later with app2sd?
thanks all for al these wonderful guide
en0203 said:
hi thanks for the steps, just to confirm a few things:
1) i think we don't need the swap partition right? swap partition is used for linux swap which only custom kernel can use right?
2) is there a way to reverse app2sd later? i am asking because i believe the froyo is near. will we have problem upgrading later with app2sd?
thanks all for al these wonderful guide
Click to expand...
Click to collapse
1) Yes, but from all the tutorials i've read they all created a swap, so I just created it incase. Better be safe than sorry
2) I'm enjoying apps2sd way to much right now to even try uninstalling it and correct me if I'm wrong when froyo update is released our phone will be back to scratch one.. so format sd card and start all over again.
This is why i'm looking into nandroid backup/open recovery right now but can't seem to find it for xt720
Have a good one,
Yash
yadvani said:
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
Click to expand...
Click to collapse
it goes endless loop. see the attachment.
can you give some details on how u use hiren boot cd to format card? (What program were you use? and how did you do?). Thanks a lot
yadvani said:
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
Click to expand...
Click to collapse
Hello i used linux gnome partition to partition my sd card (8GB) i made the 3 partition in the correct order as you instructed but when i get the sdcard in my xt720 it says blank card or unsuported filesystem and it promts me to format the card.
you said that i had to mark the partitions as active you meant to make them all primary right?
vaggoulas said:
Hello i used linux gnome partition to partition my sd card (8GB) i made the 3 partition in the correct order as you instructed but when i get the sdcard in my xt720 it says blank card or unsuported filesystem and it promts me to format the card.
you said that i had to mark the partitions as active you meant to make them all primary right?
Click to expand...
Click to collapse
Yes i forgot to mention you have to make them all primary and also mark them as active, these are two different things.
Give me sometime ill be uploading the instructions with screenshots.
spiderx_mm said:
it goes endless loop. see the attachment.
Click to expand...
Click to collapse
I didn't encounter any such problem, you may have better luck trying the Apps2sd forum. BTW stupid question but is your device rooted. Also what step did you encounter the problem, I may be able to repeat it and try and solve it.
Sorry not a dev just a user
Partition Tutorial with Screenshots
1) Download Hiren's Boot Cd (search torrent sites). The screenshots I am providing are using Hiren's Boot CD 10.6
2) Boot from the CD
3) Choose "Boot Mini Xp/Windows" (sorry no screenshots: boot menu)
4) Once minixp is loaded, connect your milestone with memory card access.
5) Heres where the screenshots start
6) Mount your milestone by double-clicking "Mount Removable" on the desktop
7) Check My Computer if your SD Card has been mounted. Mine as per the image is E: FAT32
8) Run "HBCD Menu" from the desktop and you should get the below image
9) Run Partition Wizard Home Edition
10) This is my setup below
11) Like I mentioned before create three primary partitions in the following order: FAT32; EXT2/3; SWAP as per your size preference. Don't forget ext2/3 partition is used for applications and fat32 for media
12) Here is how you mark them active and primary
13) Apply the changes by clicking the green arrow or apply button
14) Once the operation is done, exit the app and then safely remove your disk
15) Hopefully if everything went well, your milestone will now detect the sd card. If not try restarting
16) If all went well restart anyways and then follow the above steps to adb into your device and install apps2sd. Don't forget to enable USB debugging for it.
Long post I know... tried to be as descriptive as possible.
have a good one
spiderx_mm said:
it goes endless loop. see the attachment.
Click to expand...
Click to collapse
When doing this step Type: sh install_use_busybox.sh (trigger installation of App2SD)
try Type: sh install_use_busybox.sh -f
to force the installation ..
also try this thread other people have faced similar problem
sorry can't be of more help .. try re-doing the steps..
just wanna add that this works on the Milestone XT720.
but i might add that the script doesn't remove the backups made so you have to manually remove the backups created by the script. the backup folders are:
Code:
/data/app-private1
/data/app1
/data/dalvik-cache1
thanks
ok i did it!!! thx everybody!!!
Related
(STEP 1 GOLDCARD)
Finaly i done it all phew i had a really long day learning yesterday from the start i was on the tmobile latest rom RUU_Hero_TMobile_UK_2.73.110.26_release_signed_NoDriver.exe
I figured out the goldcard soulotion http://forum.xda-developers.com/showthread.php?t=572683
Great video guide here http://theunlockr.com/2009/10/18/how-to-downgrade-your-htc-hero-so-it-can-be-rooted/
01. Download QMAT 5.06 here http://revskills.de/downloads/qmat_506.zip
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work. Note sd card must be in phone here
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here http://revskills.de/pages/goldcard.html to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here http://download.cnet.com/HxD-Hex-Editor/30....html?tag=mncol
13. Install and launch HxD Hex Editor program. Note SD Card has to be in your pc or reader here at this point NOTE ALSO (run the editor as administrator in order for it to appear)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 here ftp://xda:[email protected]/Hero...ed_NoDriver.exe
from which you can fastboot boot and/or root your phone with flashrec Here http://forum.xda-developers.com/showthread.php?t=559613 (Please see guide below for this)
Done.
(STEP 2 recovery)
You need to install this recovery first with flashrec instructions below
You can use flashrec to flash the patched recovery, from where you can do all the usual stuff (and even put the old hboot back on if you want!)
Notice:
flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working.
So for now it's ok but a next version might have patched this, so keep this in mind !
Quick Howto:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
flashrec-20090815.apk
Cyanogen’s / Modaco Hero Recovery Image
Update: updated flashrec here
6. Extract the cm-hero-recovery.img out of the MoDaCoPatchedRecovery-1.0.zip and put it somewhere on your computer.
7. Save both the cm-hero-recovery.img and the flashrec-20090815.apk to your computer, then copy them both to your SD card
(do NOT put them inside any folders on the SD card, just put them in the root of the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
9. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
10. Open the file manager and goto SDCard and then find the flashrec-20090815.apk file and click on it.
If asked, tell it to use Package Installer to open it. It should automatically install the apk.
11. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
12. Once done, click on the empty text box in the FlashRec program and type:
sdcard/cm-hero-recovery.img
Then click on the Flash Custom Recovery Image button and wait for it to finish.
13. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on
(keep holding until the recovery screen comes up has a bunch of text on a black background).
As long as that screen comes up, you have done it correctly and can now go and load other ROM/hboot/whatever.
THIS IS OPTIONAL RECOVERY BELOW BETTER OPTIONS BUT YOU NEED THE ABOVE RECOVERY FIRST
I then flashed the new recovery-RA-HERO-v1.2.3 Great Video guide here http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
http://forum.xda-developers.com/showthread.php?t=561124
There are several ways to install a custom recovery, choose the one that suits you most
via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Code:
Copy recovery-RA-HERO-v1.2.3.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-HERO-v1.2.3.img
(STEP 3 INSTALL CUSTOM ROM)
Then i installed the cool modaco custom rom v2.8 to my phone http://android.modaco.com/content/htc-hero...com/292018/xda/
Great Video guide here http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
Also dont forget to upgrade your radio here http://android.modaco.com/content/htc-hero...ate-zip-format/
Download the latest one normally on the top to install rename the zip to Update put on root of SD card and boot into recovery and install update.zip option easy as that.
STEP 4 PARTITION SD CARD)
Then finaly i partioned my sd card using the recovery imiage with thease commands directly from the phone in recovery.
I ran the following commands in this order from recvoery mode:
- Wipe data + cache (factory reset)
- Wipe ext partition on SD-card
- Wipe Dalvik-cache on SD-card (NOT on /data !) [email protected] ALWAYS WORK
- Partition SD-card : 500MB Ext2, 32MB Swap, remaining Fat32
- Convert ext2 to ext3
- Installed ROM
ANOTHER GREAT GUIDE HERE FOR WINDOWS TERMINAL USERS http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
what a nice day and now i have a super hero
PS ANY QUESTIONS I WOULD BE GLAD TO HELP WITH ANY PROBLEMS THATS WHAT I AM HERE FOR THANKS.
Mods if you think this is usefull for noobs then you may sticky if you want thanks to all.
If anyone wants to add anything or finds something wrong with the guide please let me know so i can edit it thanks to all that made this possible.
hi, i got an error 170 when trying to do step 20 in section 1(downgrade rom)!
GaRd3NiA said:
hi, i got an error 170 when trying to do step 20 in section 1(downgrade rom)!
Click to expand...
Click to collapse
you could have not done the steps corectly my advice is to start again from the start.
What is the point of this gold card process? Noobish question i am sure just i have a rooted phone already so will this give me anything additonal guys? Ta
MojUk said:
What is the point of this gold card process? Noobish question i am sure just i have a rooted phone already so will this give me anything additonal guys? Ta
Click to expand...
Click to collapse
the point of this is for users that upgraded to the new rom and can't downgrade back and updated there hboots u need the goldcard the rest is all optional hence the road to freedom for your hero.
need help
hi. is this procedure it will work with Htc Hero from Hong Kong? i was trying several procedures founded on google, but no one worked.
QMAT 5.06 link has changed
https://ssl.webpack.de/revskills.de/pages/download.html
HTC Hero problems after gold card procedeure
jutley said:
(STEP 1 GOLDCARD)
Finaly i done it all phew i had a really long day learning yesterday from the start i was on the tmobile latest rom RUU_Hero_TMobile_UK_2.73.110.26_release_signed_NoDriver.exe
I figured out the goldcard soulotion http://forum.xda-developers.com/showthread.php?t=572683
Great video guide here http://theunlockr.com/2009/10/18/how-to-downgrade-your-htc-hero-so-it-can-be-rooted/
01. Download QMAT 5.06 here http://revskills.de/downloads/qmat_506.zip
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work. Note sd card must be in phone here
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here http://revskills.de/pages/goldcard.html to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here http://download.cnet.com/HxD-Hex-Editor/30....html?tag=mncol
13. Install and launch HxD Hex Editor program. Note SD Card has to be in your pc or reader here at this point NOTE ALSO (run the editor as administrator in order for it to appear)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 here ftp://xda:[email protected]/Hero...ed_NoDriver.exe
from which you can fastboot boot and/or root your phone with flashrec Here http://forum.xda-developers.com/showthread.php?t=559613 (Please see guide below for this)
Done.
(STEP 2 recovery)
You need to install this recovery first with flashrec instructions below
You can use flashrec to flash the patched recovery, from where you can do all the usual stuff (and even put the old hboot back on if you want!)
Notice:
flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working.
So for now it's ok but a next version might have patched this, so keep this in mind !
Quick Howto:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
flashrec-20090815.apk
Cyanogen’s / Modaco Hero Recovery Image
Update: updated flashrec here
6. Extract the cm-hero-recovery.img out of the MoDaCoPatchedRecovery-1.0.zip and put it somewhere on your computer.
7. Save both the cm-hero-recovery.img and the flashrec-20090815.apk to your computer, then copy them both to your SD card
(do NOT put them inside any folders on the SD card, just put them in the root of the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
9. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
10. Open the file manager and goto SDCard and then find the flashrec-20090815.apk file and click on it.
If asked, tell it to use Package Installer to open it. It should automatically install the apk.
11. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
12. Once done, click on the empty text box in the FlashRec program and type:
sdcard/cm-hero-recovery.img
Then click on the Flash Custom Recovery Image button and wait for it to finish.
13. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on
(keep holding until the recovery screen comes up has a bunch of text on a black background).
As long as that screen comes up, you have done it correctly and can now go and load other ROM/hboot/whatever.
THIS IS OPTIONAL RECOVERY BELOW BETTER OPTIONS BUT YOU NEED THE ABOVE RECOVERY FIRST
I then flashed the new recovery-RA-HERO-v1.2.3 Great Video guide here http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
http://forum.xda-developers.com/showthread.php?t=561124
There are several ways to install a custom recovery, choose the one that suits you most
via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Code:
Copy recovery-RA-HERO-v1.2.3.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-HERO-v1.2.3.img
(STEP 3 INSTALL CUSTOM ROM)
Then i installed the cool modaco custom rom v2.8 to my phone http://android.modaco.com/content/htc-hero...com/292018/xda/
Great Video guide here http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
Also dont forget to upgrade your radio here http://android.modaco.com/content/htc-hero...ate-zip-format/
Download the latest one normally on the top to install rename the zip to Update put on root of SD card and boot into recovery and install update.zip option easy as that.
STEP 4 PARTITION SD CARD)
Then finaly i partioned my sd card using the recovery imiage with thease commands directly from the phone in recovery.
I ran the following commands in this order from recvoery mode:
- Wipe data + cache (factory reset)
- Wipe ext partition on SD-card
- Wipe Dalvik-cache on SD-card (NOT on /data !) [email protected] ALWAYS WORK
- Partition SD-card : 500MB Ext2, 32MB Swap, remaining Fat32
- Convert ext2 to ext3
- Installed ROM
ANOTHER GREAT GUIDE HERE FOR WINDOWS TERMINAL USERS http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
what a nice day and now i have a super hero
PS ANY QUESTIONS I WOULD BE GLAD TO HELP WITH ANY PROBLEMS THATS WHAT I AM HERE FOR THANKS.
Mods if you think this is usefull for noobs then you may sticky if you want thanks to all.
Click to expand...
Click to collapse
hi, was following your procedure in order to crezte the Gold Card. Everything goes perfect up to step 20. After I used to flash with RUU_Hero_HTC_WWE_2.73.405.6_WWE_release_signed_NoDriver.exe; big mistake. after flashing I can't put phone in recovery mode, it showing a triangle with a exclamation mark in the center, also GPS is not existing at all, 3 G network not present. My phone has been bought from Hong Kong.
I was trying to follow the steps to recovery but useless; flashrec-20090815.apk is not working, even the new versions. If someone can help me with some advices, i'm really desperate. thanks
help please!!!!
Hi all. after I create the gold card, see link http://forum.xda-developers.com/showthread...187#post5036187, I RUU my Htc Hero from Hong Kong with SEA: (South East Asia)
RUU_Hero_HTC_Asia_SEA_WWE_2.73.728.5_release_signe d_NoDriver.exe and I'd seen there is no GPS, Market and 3G, than I'd applied another RUU RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe and this time I have Market, but still no GPS and 3G. I tried different RUU from http://forum.xda-developers.com/showthread.php?t=559622, but no one working, not even the previous two. I tried to use flashrec-20090815.apk in order to flash, but no working. even the new version of flashrec not working. I tried to put in recovery mode holding POWER + HOME button, but after boot is showing a triangle with exclamation mark in the middle. Same is happening if I try to go in recovery mode from ADB (command adb shell reboot recovery). Is somebody so kind to explain me what to do in order to restore my phone at least how it was before, please? My skills in android development are 0. thanks
help please!!!!
so, nobody wants to help me ? i'm really desperate ...........
finally, I made again the gold card, after I re flash with RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe, and works. Than I used flashrec-1.1.3-20091107-2.apk and recovery-RA-hero-v1.5.2.img and I created Backup.img. Tried to put in recovery mode by pressing in the same time Power and Home and I got the following screen:
"reboot system now [Home+Back]
apply sdcard:update.zip [Alt+S]
wipe data/factory reset [Alt+W]"
"E:Can't open /cache/recovery/command"
BTW, GPS and 3G still missing from menu. Trying to update with 2.8-update-hero-modacocustomrom-core-chinese-signed.zip or with 3.0-update-hero-modacocustomrom-core-signed.zip, I got this :
" -- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (663 files)
E:Verification failed
Installation aborted."
Phone hanging, freezing.... HELPPPPPP please!!!!!!!!
I forgot to mention these details:
Original version
phone type is EBI132A
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 44690c1a
Build no: 2.73.721.9 **146733 CL#62020
Soft Version 1.0.0.A 6288
Actual version
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 8dd6deee [email protected])
Build no: 2.73.405.5**146733 CL#61267
Soft Version 1.0.0.A 6288
this is what I got:
What else i can do?
Is there anyone here in this forum who has been complimentary to this guide? I ask because I am an organizer of the recognition awards for Achievement in Technical Writing & Guides (to help people use their phones)... And the Android forums are new, and thus there has been very little response to the intention to recognize those who have contributed knowledge, apps, themes, guides to the community.
thank you. see my sig.
ovigt71 said:
I forgot to mention these details:
Original version
phone type is EBI132A
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 44690c1a
Build no: 2.73.721.9 **146733 CL#62020
Soft Version 1.0.0.A 6288
Actual version
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 8dd6deee [email protected])
Build no: 2.73.405.5**146733 CL#61267
Soft Version 1.0.0.A 6288
Click to expand...
Click to collapse
Hi, I have the exact same hero as you do (same system etc..). Didn't work with the "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe"
so am now about to try it with this one:
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
but after reading you post I am a lil weary...
is you hero still not working 100%??
Thx
1. Bricked my rooted G2 with 2.1 rom by interrupting the radio update process
2. Got it back within 5 days repaired in warranty FOC! mainboard replaced.
3. Flashrec backup recovery did not work, so had to go into goldcard method. (2.73.110.26 CL#69351)
4. Update succesfull. I thank you very much for your efforts Even the ugly static G2 T-Mobile screen now says HERO
5. Linda File Manager + FlashREC
6. Backup recovery -> Backup complete
THANKS
I got a Customer Id Error when I try to install either
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed _NoDriver.exe
or
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe
I thought the purpose of the GoldCard was to help bypass the ID checking?
bob_harris said:
I thought the purpose of the GoldCard was to help bypass the ID checking?
Click to expand...
Click to collapse
It is - the point is that the creation of a goldcard is not an exact science. If your goldcard is not correct, for any reason, it won't work.
There have been many accounts on these forums of people having to try 3 or 4 times (usually using different SD cards) before getting a goldcard that works.
Regards,
Dave
foxmeister said:
It is - the point is that the creation of a goldcard is not an exact science. If your goldcard is not correct, for any reason, it won't work.
There have been many accounts on these forums of people having to try 3 or 4 times (usually using different SD cards) before getting a goldcard that works.
Regards,
Dave
Click to expand...
Click to collapse
I got it working on the second attempt. In the tutorial I was reading it advice I use a separate sd card reader when creating the gold card.
On my second attempt I just left the card in the phone the whole time and mounted it through the phone when I needed to perform hex editing on it.
Lovely job, now to choose what custom ROM I shall flash.
How-TO Root the
HTC Slide
HTC Aria + See this Link > http://forum.xda-developers.com/showthread.php?t=708233
&
Nexus One
Works With ALL 2.1 HTC PHONE"S with 2e Recovery!
Must be able to See the Device From the ADB in recovery for it to work!
See this Thread if you Have a New Slide or Updated the OTA to version 1.35.531.1
http://forum.xda-developers.com/showthread.php?t=754669
If at anytime You have Trouble or Can't get my Method to work, Please see wesgarner's [Root] SimpleRoot v1.3 (Linux/Windows)
Link > http://forum.xda-developers.com/showthread.php?t=713347
Just use my Update.zip if you just want root only
Download This Package > Root.zip
*EDITED* 6/29/2010 Update Now Contains Su & Superuser.apk. Permission Fixed on SU / Sh as well
-Contains Dusty51 script for Partitioning the a2sd & Swap
-fstab install so swap will work
-Default partition table's are:
-Linux Swap @ 32mb
-ext2 a2sd partition @ 512mb
-Fat32 Partition is based on the size after the 2 above
How-to Use:
Once You load the Recovery via update.zip, Unplug & Plug the USB to make sure the Device is Seen..
- Open Command Prompt from Computer
- Adb shell
- sdparted
- Next Follow the Command, y = Y to confirm..
Note: Backup your SDCARD first, only thing should be on it is the update.zip then Follow the above to Format for a2sd support!
Click to expand...
Click to collapse
Stratis1978 said:
I've got root now and just wanted to repeat what made the difference for me (also posted pages back):
when you're ready to run recovery in the bootloader be sure to unplug the USB from your phone until 'HBOOT' not 'HBOOT USB PLUG' displays.
So basically you unplug the phone until 'HBOOT' appears, have 'RECOVERY' highlighted, and plug the phone in a moment before you select 'RECOVERY'.
The moment I did that I had 'recovery' displaying in my loop.
Continue with the directions...
Click to expand...
Click to collapse
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Step 0.
Un-zip the Package you Downloaded
Step 1.
Place the Contents of "update.zip" & "ota.zip" & "loop" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like) ( ./ Is used For OSX )
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Hit Volume Up + Power button to Bring up the Selectable Menu
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please.)
Step 11.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
This is the Command, We do not Push this Yet adb push update.zip /sdcard
Click to expand...
Click to collapse
step 12.
Hit run update.zip, as soon as you see a Little Bar appear under the text, push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 13.
In successful, you should see Clockwork Recovery & you Now have Su & Superuser.apk Installed! You can Now Reboot Your Phone into the OS to verify.
If unsuccessful, repeat steps 11 & 12.
Congrats.
Next Guide For Flashing the ENG-BUILD with Test-key Recovery http://forum.xda-developers.com/showthread.php?t=703076
Updating the Radio Once Everything Is Done http://forum.xda-developers.com/showthread.php?t=705064
Special Thanks to:
Paul O'Brien: > http://android.modaco.com/forum.html
Koushik K. Dutta: His ClockWorkMod Recovery can Be found here > http://www.clockworkmod.com/
&
http://unrevoked.com/ OTA Spoofing Method
&
ChiefzReloaded for Huge amount of Suggestion & Brain Storming.
GREAT JOB!
Thank you sir, for your diligence, and hard work! Let's get to work boys!!!
Tips: May want to be a little more clear on "SDK Directory". Some may think that you "must" have this directory, but all that is important to know is that you know the directory where the contents were placed... If that IS the case, then I'd mention that...
Also, might be important to mention the phone should already be plugged in, and should have prerequisite of ADB working...
Thaaaaaaank you! got some fun stuff to do right after work now
Re: How-TO * Root The Slide * *6/15/2010*
Thanks guys. You've made a lot of people happy.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Having trouble at step 5. ADB works when the phone is powered on. However, when in Recovery, adb devices list is blank.
Other problems: is Step 8 really a step? It says to select Update.zip... is this just anecdotal, as in "Now we will select an update.zip"...?
And how are you "selecting" things in Recovery? My recovery simply has the phone with a triangle...
What is ADB i come from rooting g1 and i dont remember or know what it is i rooted my g1 when it first came out and every since then all i had to do is name file update then push. could u be alittle more clear for a retard like me I dont want to miss my phone up when i just got it today, I really want to get rid of some of the bloatware on it tho
richierich118 said:
What is ADB i come from rooting g1 and i dont remember or know what it is i rooted my g1 when it first came out and every since then all i had to do is name file update then push. could u be alittle more clear for a retard like me I dont want to miss my phone up when i just got it today, I really want to get rid of some of the bloatware on it tho
Click to expand...
Click to collapse
ADB is part of the Android SDK, you'll need to download it and extract it to your PC before you can use it.
http://developer.android.com/sdk/index.html
My problem may be that I'm using a Mac, but I cannot get my Terminal to recognize the "loop" command. I've tried many things and it won't work properly just keeps giving me errors. I'm gonna keep trying though.
android007 said:
My problem may be that I'm using a Mac, but I cannot get my Terminal to recognize the "loop" command. I've tried many things and it won't work properly just keeps giving me errors. I'm gonna keep trying though.
Click to expand...
Click to collapse
Loop is just a batch file (.bat). I don't know about Macs using batch files. All it's doing is looping the "adb devices" command to see if it detects the device.
fermunky said:
Having trouble at step 5. ADB works when the phone is powered on. However, when in Recovery, adb devices list is blank.
Other problems: is Step 8 really a step? It says to select Update.zip... is this just anecdotal, as in "Now we will select an update.zip"...?
And how are you "selecting" things in Recovery? My recovery simply has the phone with a triangle...
Click to expand...
Click to collapse
You have to Repeat then... It Don't always work everytime!! That's why I said Repeat.. You have to Power Off, run loop & if you see now Devices then you have to Repeat again!!
You Must boot into bootloader First!! Run Loop, Then to Recovery!
my computer doesn't find the device in recovery mode. Any advice on getting around this? adb works when phone is on.
eugene373 said:
You have to Repeat then... It Don't always work everytime!! That's why I said Repeat.. You have to Power Off, run loop & if you see now Devices then you have to Repeat again!!
Click to expand...
Click to collapse
Wow, cant believe I missed that order. May need to update the how to though... it says to run loop, then go to bootloader, then to recovery. You need to add a step after getting into bootloader of "Wait for device to be listed, then goto recovery"... or similar.
My error when trying to invoke the loop file:
: command not founde 1: :TOP
sdk/tools/loop: line 2: adb: command not found
sdk/tools/loop: line 3: GOTO: command not found
Click to expand...
Click to collapse
Sweeeet! Awesome job guys.
On Mac replace the loop.bat with loop.sh and change the contents of the file to the following:
#!/bin/bash
while [ 1 ]
do
adb devices
done
On the command line, run "chmod 755 loop.sh" to give it execute permission. To run the file type "./loop.sh"
Are there any roms for it yet?
android007 said:
My error when trying to invoke the loop file:
Click to expand...
Click to collapse
You have not added the tools directory to your PATH system variable. Explained on the SDK page. Also, you don't need to be in the /tools folder, just go to the folder you extracted the files to.
Eugene, I noticed while the loop was running, I chose recovery, and on one instance, I saw an offline device, but then subsequent loop commands, it stopped listing them. Also, it is still not clear what to do on Step 8. Most of us only see an image in recovery, no menus.
With no menus, anyone know how to reboot the phone in recovery other than removing the battery?
marvinp said:
On Mac replace the loop.bat with loop.sh and change the contents of the file to the following:
#!/bin/bash
while [ 1 ]
do
adb devices
done
On the command line, run "chmod 755 loop.sh" to give it execute permission. To run the file type "./loop.sh"
Click to expand...
Click to collapse
you think you can do quick little rewrite of the tutorial for us mac users
HOW-TO Root the Slide
(MAC OSX FLAVORED) KAPOWWW!!!!
&
Android SDK on Mac
STEP 1.
Download Android SDK from here.
STEP 2.
Unzip it. Place the folder it creates in your Documents folder and rename it AndroidSDK or SDK. (Something Easy)
SUCCESS!!! Android SDK Installed… //WTF!!??!!
STEP 3.
Download This Package > Slide Root.zip
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
(These five files need to be placed DIRECTLY into the AndroidSDK/tools/ folder)
STEP 4.
RENAME Loop.bat to Loop.sh, then right click, open with TEXTEDIT.
Delete it’s contents and replace it with
#!/bin/bash
while [ 1 ]
do
adb devices
done
Save and Close the File.
STEP 5.
On your Slide, GO TO Settings > Application > Development and turn on USB Debugging.
This should save you headaches.
NOW… Power Off the Slide
STEP 6.
OPEN Terminal
(APPLE + SPACE and type Terminal, press enter.)
Now, CD to the SDK/Tools Directory.
It should be where we left it.
/Users/YOURUSERNAME/Documents/AndroidSDK/tools/
Terminal SHOULD open with it already in your USERNAME
Type cd Documents/AndroidSDK/tools/
STEP 7.
Power On the Slide into the Bootloader by Holding Down ( Volume Down + Power Button )
STEP 8.
NOW run your loop file (the one we made earlier)
The Terminal should be all queued up to the Tools folder.
Type in ./loop.sh
(The Terminal should be blowing up with List of Devices Attached over and over)
STEP 9.
Once your loop is running, select Recovery from the bootloader menu.
(Volume UP & DOWN to change selection and POWER to Select)
STEP 10.
When recovery loads, you should Have an Offline Device.
The Slide’s screen will have a picture of a Phone and RED triangle around a !
(Don’t freak out, this is a good thing.)
Hit Ctrl + C to stop your script & see.
If this doesn't happen, Power Off and try again from STEP 7.
STEP 11.
Un-plug your USB cable from your Slide & Plug it back in for it to Detect ADB Correctly!!!
IMPORTANTE!!!
At this point you can adb devices to see if it detects your device and that it is in recovery mode.
Type into Terminal ./adb devices
If it says recovery you are golden and move onto STEP 12 to kick the habit.
If not, rinse and repeat from STEP 7.
STEP 12.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
STEP 13.
Type into Terminal
./adb push ota.zip /sdcard/update.zip
STEP 14.
Type into Terminal
./adb push slideroot.zip /sdcard
STEP 15.
MUY IMPORTANTE!!!
Have this Command ready in your Terminal before applying update.zip again!!
./adb push update.zip /sdcard
STEP 16.
On your Slide, Hit run update.zip
As soon as you see A Little Bar appear behind the text
Push ENTER to execute the Terminal command
(./adb push update.zip /sdcard )
STEP 17.
If successful, you should see Clockwork Recovery.
If unsuccessful, repeat steps 13-16.
STEP 18.
In Clockworkmod Recovery,
Go to the Partitions menu and Mount System
(It should be at the top and the only one not mounted.)
STEP 19.
Go one level back & select install any zip from sdcard.
Select slideroot.zip & apply update from zip
(This will finish the Root process).
STEP 20.
Reboot your phone & wait for it to load completely.
To confirm that your slide is connected as a device use the command ./adb devices
If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
STEP 21.
./adb install Superuser.apk
(If it says it cannot locate directories, make sure you can find your device
using ./adb devices… If things still don't work, my best advice is to start over)
STEP 22.
After Superuser is installed try to use adb to shell to your device.
Type in Terminal
./adb shell
you will get a $
Then type su
On the Slide, Superuser should pop-up asking if you give permission, do so.
In Terminal, your $ should turn into a #. If so, you have root. WOOT!!!
Original SHOUT OUTS!!!
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method
&
ChiefzReloaded for Huge amount of Suggestion & Brain Storming.
But most of all, you should thank eugene373 for rooting the slide and not sleeping for two days.
His original post is here.
sk8rbebop said:
STEP 14.
Type into Terminal
./adb push slideroot.zip
Click to expand...
Click to collapse
should it not be:
./adb push slideroot.zip /sdcard
Also...
sk8rbebop said:
STEP 15.
VERY IMPORTANTE!!!
Click to expand...
Click to collapse
Should be:
MUY IMPORTANTE!!!
I don't understand the need for a separate post when the only difference between osx and windows is that osx uses a shell script and windows a batch file and osx is discussed in the post about rooting.
nerdcorerising said:
I don't understand the need for a separate post when the only difference between osx and windows is that osx uses a shell script and windows a batch file and osx is discussed in the post about rooting.
Click to expand...
Click to collapse
Five different people asked for it so they got it.
Thanks!
Thanks a bunch for the tutorial! We really do appreciate it. I just had a couple questions about 2 of the steps.
STEP 6.
OPEN Terminal
(APPLE + SPACE and type Terminal, press enter.)
Now, CD to the SDK/Tools Directory.
It should be where we left it.
/Users/YOURUSERNAME/Documents/AndroidSDK/tools/
Terminal SHOULD open with it already in your USERNAME
Type cd Documents/AndroidSDK/tools/
I got lost where it says "Now, CD to the SDK/Tools Directory." I do not really know what the CD means and what I should be typing into Terminal?
Also should my phone already be plugged in to my Mac?
Please let me know and thanks!
Thanks a bunch for this tutorial. I am about to try to ROOT, it should go over smoothly. Now from the ROOT what else have you guys been doing to you're Slide? I know Cyanogen has not said much, that is who I used for my myTouch 3G and my G1.
Click to expand...
Click to collapse
I flashed the Eng Build, then SlideMEROOT2 and then the new radio (you need this). Just follow the how-to's already posted, but remember to type ./ before the commands in Terminal.
Ex. ./adb devices Instead of adb devices.
There were a couple people who were trying to keep their original stock rom, but slidemeroot2 is basically the original rom. Plus, someone posted the original stock backup, so flash away.
-------------------------------------
Sent via the XDA Tapatalk App
this is wrong
#!/bin/bash
while [ 1 ]
do
adb devices
done
it should be
#!/bin/bash
while [ 1 ]
do
./adb devices
done
shadowleo85 said:
this is wrong
#!/bin/bash
while [ 1 ]
do
adb devices
done
it should be
#!/bin/bash
while [ 1 ]
do
./adb devices
done
Click to expand...
Click to collapse
It's no more "wrong" than your code...
The first assumes that you've configured your shell to link the "adb" command to the adb "app" in the sdk/tools directory. Your code assumes that you will be activating the script while "within" that very directory.
The code, IMHO, should read:
Code:
...
[PATH TO SDK/TOOLS/]adb devices
...
And the OS X user should be instructed to insert their own path.
HebrewToYou said:
It's no more "wrong" than your code...
The first assumes that you've configured your shell to link the "adb" command to the adb "app" in the sdk/tools directory. Your code assumes that you will be activating the script while "within" that very directory.
The code, IMHO, should read:
Code:
...
[PATH TO SDK/TOOLS/]adb devices
...
And the OS X user should be instructed to insert their own path.
Click to expand...
Click to collapse
WRONG the code running in the shell is to continuously run adb devices... which to do so correctly would have to be implemented with ./ in front to run correctly on a mac... dont try to correct what is right i will school u
and seeing as he clearly instructs u to place those apps within the tools folder and "cd" to it... means that the user should have those commands ready at hand which is included in the folder...
shadowleo85 said:
this is wrong
#!/bin/bash
while [ 1 ]
do
adb devices
done
it should be
#!/bin/bash
while [ 1 ]
do
./adb devices
done
Click to expand...
Click to collapse
Ur right.. that is the right way..
also for those of u having problems with the loop step where it never sticks... try a different memory card... i was having problems with the stock card... so i tried a different card and it worked perfectly... with no problems
shadowleo85 said:
and seeing as he clearly instructs u to place those apps within the tools folder and "cd" to it... means that the user should have those commands ready at hand which is included in the folder...
Click to expand...
Click to collapse
LOL. Okay, tough guy.
The fact is that the active directory in your terminal is irrelevant to the actual rooting process. If you want to argue about it, have at it. I really don't care.
Yes, in terminal you must type ./adb devices, but within the .sh you can just issue adb devices and it works just fine. It is because you are issuing a command from within a script and OS X understands you better when you use them.
As for the memory card trick everyone is perpetuating, tis but a superstition and whatever floats your boat, while you attempt to get adb to stick. When I rooted mine, it took five to ten tries. Rooting my girlfriend's, on the other hand, took nearly 15-20 min for it to catch.
sk8rbebop said:
Yes, in terminal you must type ./adb devices, but within the .sh you can just issue adb devices and it works just fine. It is because you are issuing a command from within a script and OS X understands you better when you use them.
As for the memory card trick everyone is perpetuating, tis but a superstition and whatever floats your boat, while you attempt to get adb to stick. When I rooted mine, it took five to ten tries. Rooting my girlfriend's, on the other hand, took nearly 15-20 min for it to catch.
Click to expand...
Click to collapse
within the shell command command it has to be ./adb devices or it fails at command line 4 which is the problem i was having until i changed it in the shell and it worked... along with a few others...
and as far as the memory card thats the issue... i tried 5 different memory cards one always worked the others never stuck... it may have something to do with the way the memory card is coded... my 16gb mem card out my hd2 is the only one that worked... not really a superstition
shadowleo85 said:
within the shell command command it has to be ./adb devices or it fails at command line 4 which is the problem i was having until i changed it in the shell and it worked... along with a few others...
and as far as the memory card thats the issue... i tried 5 different memory cards one always worked the others never stuck... it may have something to do with the way the memory card is coded... my 16gb mem card out my hd2 is the only one that worked... not really a superstition
Click to expand...
Click to collapse
The memory card has nothing to do with the rooting process whatsoever. With that said, a lot of the memory cards shipping with the slides are misformated. The first thing I did was backup my card, swap it out with a class 10 16 GB card and set up a 1GB ext4 partition. Then I copied the files back to the FAT partition and all was well.
HebrewToYou said:
The memory card has nothing to do with the rooting process whatsoever. With that said, a lot of the memory cards shipping with the slides are misformated. The first thing I did was backup my card, swap it out with a class 10 16 GB card and set up a 1GB ext4 partition. Then I copied the files back to the FAT partition and all was well.
Click to expand...
Click to collapse
yet with all the cards i tested which are formatted correctly and running perfectly on all my devices... and even tried useing my class 6 8gig with is partitioned for my og mytouch didnt work... dude stop trying to correct me i got this... worry bout ya own lil world
shadowleo85 said:
yet with all the cards i tested which are formatted correctly and running perfectly on all my devices... and even tried useing my class 6 8gig with is partitioned for my og mytouch didnt work... dude stop trying to correct me i got this... worry bout ya own lil world
Click to expand...
Click to collapse
Oy vey. Seriously? The rooting process is a hit or miss operation. Your sdcard doesn't even come into play for a second. You could probably remove the darn thing and be successful.
Please, for heaven's sake, just listen to sk8rbebop, myself or any of the numerous other people saying in no uncertain terms that the sdcard issue is a myth. Don't perpetuate something that is entirely unrooted in reality.
Sheesh...
HebrewToYou said:
Oy vey. Seriously? The rooting process is a hit or miss operation. Your sdcard doesn't even come into play for a second. You could probably remove the darn thing and be successful.
Please, for heaven's sake, just listen to sk8rbebop, myself or any of the numerous other people saying in no uncertain terms that the sdcard issue is a myth. Don't perpetuate something that is entirely unrooted in reality.
Sheesh...
Click to expand...
Click to collapse
how can it be unrooted in reality when in reality it works and im proving that... its mighty funny that it doesnt stick unless this specific memory card is in my device... and u stating that it doesnt come into play is wrong... when u load ur phone into bootloader it does check ur "memory card" for an nbh image which is where i believe the problem lies... it accesses ur memory card just like the og mytouch did to locate a gold card... dont argue with me when it is just another work around that just may work seeing as IM PROVING THAT IT DOES INDEED WORK
shadowleo85 said:
how can it be unrooted in reality when in reality it works and im proving that... its mighty funny that it doesnt stick unless this specific memory card is in my device... and u stating that it doesnt come into play is wrong... when u load ur phone into bootloader it does check ur "memory card" for an nbh image which is where i believe the problem lies... it accesses ur memory card just like the og mytouch did to locate a gold card... dont argue with me when it is just another work around that just may work seeing as IM PROVING THAT IT DOES INDEED WORK
Click to expand...
Click to collapse
Oy vey. Fine, believe what you want. What's *actually* helping you root the device is sticking gum on your nose, turning your baseball cap backwards, rubbing your lucky rabbit foot and reciting the pledge of allegiance. You just haven't realized it yet.
Stay crunchy.
HebrewToYou said:
Oy vey. Fine, believe what you want. What's *actually* helping you root the device is sticking gum on your nose, turning your baseball cap backwards, rubbing your lucky rabbit foot and reciting the pledge of allegiance. You just haven't realized it yet.
Stay crunchy.
Click to expand...
Click to collapse
dude wtf is ur problem... if it can possibly help someone whose having the issue y r u having such an issue with it
I followed all of the instructions on this post:
forum.xda-developers.com/showthread.php?t=442480
No problems at all doing any of it.... BUT I have a G1 that had 1.6. Now it's 1.0. Everything seemed to work fine, but when I try to update with any ROM it does not seem to work... still 1.0.
When I restart it by holding the power and the home button I do not get the menu screen that all tutorials seem to have, I still get the Exclamation mark and have to hit Alt S.
Any suggestions? I have tried loading Cyanogen and 2 different JesusFreak versions. But no changes. ???
EDIT: Ok I just found this ...
to see is you are "rooted" download or use terminal app
At the $ prompt type su <enter>
should return a prompt now of
#
I downloaded the terminal app and it says permission denied when I type in su.
SO I guess it's not rooted...BUT everything I did with the instructions went off without a hitch. Did the telnet instructions with no problems....??? AHHHH!
NEW EDIT! OK I found this video "Rooting the G1 to Amon RA's Recovery " on you tube. Followed the simple instructions, everything worked great. So now I have 1.5.2, booted pressing home and power and got the menu screen for the first time ever. Tried to run an update and that menu screen is gone, I'm back to the exclamation point. And still su does not work in the terminal. And telnet only gives me a connection error now. PLEASE HELP!!!!
Ok I started over did ALL OF THIS:
If you have US-RC30/UK-RC8 or higher, you will first need to downgrade your phone to a previous version. (Skip these steps otherwise)
1. Format your phone's SD card to FAT32 mode:
* Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
* Click the notification, and then click "Mount".
* A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
1. Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
SO, it says I should have root now. I downloaded the terminal, typed in su and it says access denied. ???
Wow. I cant believe that not as single person is willing to help me on a forum about this subject.
So I started over for the 4th time. Again did everything, it all goes smoothly. But still do not have permission when I type in su to a terminal.
I loaded Amon Ra Recovery, then loaded signed killa 1.5.
It worked, I see 1.5, but when I reboot I do not get the menu, I still get the exclamation point..... I only get the menu on the first reboot after loading the Amon Ra Recovery.
PLEASE ANY HELP I'M DYING OVER HERE!!!
fellow g1 er
Theunlocker ddoott coom
For g1 Has two part video about going bqack to early version and then flashing foward to get root
It worked for me.
However you should be aware that their procedure uses something other than dangerecovery which cyanogemod requires. To use froyo 2.2 android.
I found this out AFTERFLASHING FROYO so now oi have to backtrack.
Thunlocker also links to a g1 android version with root whiicch what you flash last from the sd
card using amonra recovery.
I do however haave root. And the unlocker basic root rom worked well until I flash cyanogen mod rc3
But rc3 does still have root on my phone. It just doesn't run well because only danger recovery can partition the nand chip properly apparently and I haven't done that yet.
Furthermore be aware if you install gapps that there are two versions mdpi and hdpi and no one tells you but I think only mdpi works on g1 .
I found out after flashing hdpi myself.
Wish others would help.
We are the blind leading the blind.....
If you find something that gets you cyanogenmod worling with google apps market then please tell me how.
At least if you follow the unlocker videos you will have root.
Get it from their webpwage not you tube because the webpage has the steps written out as well.
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately