Woops...
Well, I was going to get a new rom for my galaxy s3 mini, I made a complete wite, formatting system/cashe/data, then I was going to install rom but I pressed "Install zip from sideload" instead of "install zip from sd card".
So, Now I'm thinking, I have a problem, because phone is asking me to send him a package, and I didn't even know where to send it...
In short I'm thinking that if I remove battery my phone will be dead until I can get a comp and flash thru that, so I don't want to do that.
How do I stop this request?
Adjin
You have to remove a battery.
Sent from my GT-N8000 using xda app-developers app
And phone will be dead?
And followup, what's sideload and what would I need to use to send rom to the device?
Will a rom in zip format work?
Could I just send a mal package, like a font? would that take me back to recovery once it's loaded?
This is to use adb to side load a ROM or another flashable to your device, so the ROM would be on PC not phone
Open a terminal/cmd in the location of ROM on PC, then type adb sideload xxx.zip
(Change xxx to name of .zip)
Now it will flash ROM, just the same as off SD
Best of luck!
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
This is to use adb to side load a ROM or another flashable to your device, so the ROM would be on PC not phone
Open a terminal/cmd in the location of ROM on PC, then type adb sideload xxx.zip
(Change xxx to name of .zip)
Now it will flash ROM, just the same as off SD
Best of luck!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sheeesh! I have DROID RAZR - the battery is not removable. The ADB can not see the phone in Recovery mode (drivers re-installation did not help). So there is no other way to stop this command at all??? PLEASE HELP a.s.a.p. I need my phone back!
Well was your phone rooted? Do you have a custom recovery? Do you have fastboot access? Has adb ever worked for you? Can you try another PC or USB cable to try and get adb working?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Well was your phone rooted? Do you have a custom recovery? Do you have fastboot access? Has adb ever worked for you? Can you try another PC or USB cable to try and get adb working?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you! False alarm. It turned out you can get out of that mode simply holding the power for about 5 seconds or more, and the phone will reboot. ADB worked fine from Eclipse just yesterday. Not sure why it was rejecting the very same phone in the Recovery mode.
Not as hard as it sounds
adjin said:
Woops...
Well, I was going to get a new rom for my galaxy s3 mini, I made a complete wite, formatting system/cashe/data, then I was going to install rom but I pressed "Install zip from sideload" instead of "install zip from sd card".
So, Now I'm thinking, I have a problem, because phone is asking me to send him a package, and I didn't even know where to send it...
In short I'm thinking that if I remove battery my phone will be dead until I can get a comp and flash thru that, so I don't want to do that.
How do I stop this request?
Adjin
Click to expand...
Click to collapse
goto recovery->adb sideload
on pc: adb sideload "ZIP NAME"
That's it the phone will receive the installation package from the usb port, this is called remote flash.
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
adjin said:
And phone will be dead?
And followup, what's sideload and what would I need to use to send rom to the device?
Will a rom in zip format work?
Could I just send a mal package, like a font? would that take me back to recovery once it's loaded?
Click to expand...
Click to collapse
Use adb push /system/font/
sideload is for zip based packages
Related
hi, i wanna install a custom rom, but i have no idea how to do it at all. i do not understand most terms used in the guide. so, can someone give me a step-by-step guide on how to install a custom rom? i've tried usin rom manager to install custom rom from SD card, howvere, it always reboots and i do not get the custom rom i want. the rom im planning to install is megatron, and im using windows vista 32 bit. i dunno if it helps. please help me
helpneeded said:
hi, i wanna install a custom rom, but i have no idea how to do it at all. i do not understand most terms used in the guide. so, can someone give me a step-by-step guide on how to install a custom rom? i've tried usin rom manager to install custom rom from SD card, howvere, it always reboots and i do not get the custom rom i want. the rom im planning to install is megatron, and im using windows vista 32 bit. i dunno if it helps. please help me
Click to expand...
Click to collapse
Ive had this trouble first post your phone model and also if your phone is running a custom recovery or is rooted.
BTW this post is gonna get moved, it is in the wrong section.
its an LG P500 and its rooted
helpneeded said:
its an LG P500 and its rooted
Click to expand...
Click to collapse
can you install custom recovery?
this is new but use this. http://forum.xda-developers.com/showthread.php?t=971245
all the data in my phone are gone. is there still a need for custom recovery? and what do i do after custom recovery?
all the info you need is in this thread including custom recovery. After the custom recovery is done you shall beableto try out any of the ROMs listed there. follow the instructions to the letter.
http://forum.xda-developers.com/showthread.php?t=901247
oh, the key combo to access your custom rom(once it is done) is Home+Volume Down+Power Button It even gives you the option to connect in usb mode so you can put the ROM you want and then disable usb mode and go back to main menu then choose flash from zip.
Omnichron said:
all the info you need is in this thread including custom recovery. After the custom recovery is done you shall beableto try out any of the ROMs listed there. follow the instructions to the letter.
http://forum.xda-developers.com/showthread.php?t=901247
Click to expand...
Click to collapse
i've tried reading all the guides. the problem is, i don't understand lots of things for example, partition the SD card.
1.Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
i understand the (swap: 0, ext: 512) part, but not the rest. sorry. im a beginner at these
all those options are available to you in the custom recovery. choose partition card.
you will need to download Android SDK from this site
http://developer.android.com/sdk/index.html
Install it then connect you phone in USB Debugging mode. It is under Settings->Applications. Bring up a comand prompt in windows and type adb shell then su Root your phone with this app first:
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
here's a screenshot of what the custom recovery should look like:
Omnichron said:
you will need to download Android SDK from this site
http://developer.android.com/sdk/index.html
Install it then connect you phone in USB Debugging mode. It is under Settings->Applications. Bring up a comand prompt in windows and type adb shell then su Root your phone with this app first:
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
here's a screenshot of what the custom recovery should look like:
Click to expand...
Click to collapse
i a problem using SDK on my pc. can i use the rom manager app on my phone and flash clockworkMod recovery on it?
Edit: i managed to go to a page that's similar to that of te screen shot. how ever, it only moves up and down with the volume button. nothing to execute and commands. home page brings it t a page wit a picture of a droid and an exclamation mark in a triangle.
Omnichron said:
you will need to download Android SDK from this site
http://developer.android.com/sdk/index.html
Install it then connect you phone in USB Debugging mode. It is under Settings->Applications. Bring up a comand prompt in windows and type adb shell then su Root your phone with this app first:
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
here's a screenshot of what the custom recovery should look like:
Click to expand...
Click to collapse
UPDATE: new sdk does not contain usb drivers/adb
adb is available here ..just unzip it to the sdk folder
http://megaupload.com/?d=RTEY0Q97
sarfaraz1989 said:
UPDATE: new sdk does not contain usb drivers/adb
adb is available here ..just unzip it to the sdk folder
http://megaupload.com/?d=RTEY0Q97
Click to expand...
Click to collapse
sorry to ask,what's adb
Now you have to download a rom of your choice and copy to SD card root and flash
Sent from my LG-P500 using XDA App
taha198 said:
Now you have to download a rom of your choice and copy to SD card root and flash
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
i've tried puttng a rom in .zip file in my SD card, then use clockworkMod rom manager to flash it. it just brings me back to the original rom. am i doing the right thing?
helpneeded said:
i've tried puttng a rom in .zip file in my SD card, then use clockworkMod rom manager to flash it. it just brings me back to the original rom. am i doing the right thing?
Click to expand...
Click to collapse
Did you wipe data/cache/android_secure/ and stuff.
johno168 said:
Did you wipe data/cache/android_secure/ and stuff.
Click to expand...
Click to collapse
ou teach me how to do that?
helpneeded said:
ou teach me how to do that?
Click to expand...
Click to collapse
do you have clock work mod recovery installed? if so, reboot into recovery. then you'll see it,.
johno168 said:
do you have clock work mod recovery installed? if so, reboot into recovery. then you'll see it,.
Click to expand...
Click to collapse
they told me toconfirm my phone model. cant find my phone model anywhere
helpneeded said:
they told me toconfirm my phone model. cant find my phone model anywhere
Click to expand...
Click to collapse
Settings, then scroll right down to the bottom "about phone" then what is the part that says "model number"
I used to flash recovery via terminal app on Nexus One, using command "flash_image". But it seems this command doesn't exist on Atrix 4G. Is it able to do this on Atrix 4G & how?
I think you have to use fastboot via USB from pc... Google it
However once you have CWM you can update via zip files within CWM
Sent from my Sony Tablet S using Tapatalk
wintermute000 said:
I think you have to use fastboot via USB from pc... Google it
However once you have CWM you can update via zip files within CWM
Sent from my Sony Tablet S using Tapatalk
Click to expand...
Click to collapse
Thanks any way.
There is an app called MOTOA4 Bootstrap that can install a CWM Recovery shipped with the app. Maybe ROM Manager would also do (not tested yet). So it's possible to change recovery within Android system (rooted). What I'm looking for is just an command line utility to flash any recovery I want.
amraamz said:
I used to flash recovery via terminal app on Nexus One, using command "flash_image". But it seems this command doesn't exist on Atrix 4G. Is it able to do this on Atrix 4G & how?
Click to expand...
Click to collapse
i think that is possible only with a recovery yet installed, to upgrade or something else
amraamz said:
Thanks any way.
There is an app called MOTOA4 Bootstrap that can install a CWM Recovery shipped with the app. Maybe ROM Manager would also do (not tested yet). So it's possible to change recovery within Android system (rooted). What I'm looking for is just an command line utility to flash any recovery I want.
Click to expand...
Click to collapse
you can flash latest cwm recovery with rom manager
hi all, i have a problem when i try to unlock the bootloader.
i connect my tab in fastboot mode, but when i enter 'fastboot.exe -i 0x0fce getvar version', the terminal display <waiting for device> and it apparently stops.
What can i do?
i have an unrooted 16GB wifi (SGP311) xperia tablet z with the last 4.2.2 update
Probably the fastboot drivers weren't properly installed. Try to install them properly (and reboot your PC afterwards) and try again.
Sent from my SGP311 using Tapatalk
Felimenta97 said:
Probably the fastboot drivers weren't properly installed. Try to install them properly (and reboot your PC afterwards) and try again.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
from the unlocking guide by sony..
"On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file."
i connect the tablet in fastboot (blue led), but windows doesn't ask me for drivers. i also delete drivers and reinstall them on sdk
oraziox said:
from the unlocking guide by sony..
"On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file."
i connect the tablet in fastboot (blue led), but windows doesn't ask me for drivers. i also delete drivers and reinstall them on sdk
Click to expand...
Click to collapse
Try installing the drivers by the Flashtool tool. If you're on Windows 8, deactivate Driver Signature Check, install the drivers by their tool, then reboot...
Sent from my SGP311 using Tapatalk
Felimenta97 said:
Probably the fastboot drivers weren't properly installed. Try to install them properly (and reboot your PC afterwards) and try again.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
Felimenta97 said:
Try installing the drivers by the Flashtool tool. If you're on Windows 8, deactivate Driver Signature Check, install the drivers by their tool, then reboot...
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
another edit lol
well now i think i have unlock the bootloader. what do i have to do for install a rom now? because i read about different kernels and similar things. i have never got device with these problems about flashing, can you explain me better? (now i have rooted with supersu and i have 2 recoveries, stock kernel)
oraziox said:
another edit lol
well now i think i have unlock the bootloader. what do i have to do for install a rom now? because i read about different kernels and similar things. i have never got device with these problems about flashing, can you explain me better? (now i have rooted with supersu and i have 2 recoveries, stock kernel)
Click to expand...
Click to collapse
Lol
Anyway, I have never installed a custom ROM with a device that has both internal and external SD cards, so I always recommend having two copies of the ROM you want, one on the internal, other in the external. Do the same with the latest Gapps.
Move them to the root of both memories. Then, boot into recovery (I think CWM is more stable), go to Install update.zip. Select "Choose from SD card, and then look for the ROM zip. Confirm you want to install. Wait until the process is complete. Do the same with the Gapps package.
Then, go back to the root menu of the recovery, and choose Factory Reset. Confirm and then reboot. Now you should have your ROM installed...
Sent from my SGP311 using Tapatalk
Felimenta97 said:
Lol
Anyway, I have never installed a custom ROM with a device that has both internal and external SD cards, so I always recommend having two copies of the ROM you want, one on the internal, other in the external. Do the same with the latest Gapps.
Move them to the root of both memories. Then, boot into recovery (I think CWM is more stable), go to Install update.zip. Select "Choose from SD card, and then look for the ROM zip. Confirm you want to install. Wait until the process is complete. Do the same with the Gapps package.
Then, go back to the root menu of the recovery, and choose Factory Reset. Confirm and then reboot. Now you should have your ROM installed...
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
Well, this is the 'normal' method. But i saw in the cyanogenmod wiki page of xperia tablet z that they use 2 strings by terminal with the device in fastboot. I have tried to flash the omnirom by recovery but the installer said "this is not sgp311/pollux windy" but i'm pretty sure that my tab hasn't got data connecting. When i 've reboot, it displayed only the Sony logo (so i fixed it with flashtool)
oraziox said:
Well, this is the 'normal' method. But i saw in the cyanogenmod wiki page of xperia tablet z that they use 2 strings by terminal with the device in fastboot. I have tried to flash the omnirom by recovery but the installer said "this is not sgp311/pollux windy" but i'm pretty sure that my tab hasn't got data connecting. When i 've reboot, it displayed only the Sony logo (so i fixed it with flashtool)
Click to expand...
Click to collapse
Extract the update-script of the zip,delete the lines that says :
Get.build.prop, save (make sure the file type is the same), add back and try again...
Sent from my LT26i using Tapatalk 4
Felimenta97 said:
Extract the update-script of the zip,delete the lines that says :
Get.build.prop, save (make sure the file type is the same), add back and try again...
Sent from my LT26i using Tapatalk 4
Click to expand...
Click to collapse
tried but recovery send me an error. still unable to install it
now i have a big problem: flashtool get stuck when i try to flash a new firmware!!
the tablet stay at the SONY logo and it doesn't do anything
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
once i enter recovery and use the adb sideload command i get the following error:
device not found
vivalamoza said:
once i enter recovery and use the adb sideload command i get the following error:
device not found
Click to expand...
Click to collapse
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
dbolivar said:
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
Click to expand...
Click to collapse
PLEASE DO NOT TOUCH THE INCREMENTAL OTA ZIP ON NON-GPE DEVICE!
bootloader/modem and lots of other things are getting patched!
wait for the fill flash zip and then port that...
What happens if I click restart and install that notification won't go away
Sent from my C6806_GPe using XDA Premium 4 mobile app
Okay restoring from the full 4.4.2 OTA then sideloading of the 4.4.3 OTA worked.
Definitely not as using fastboot....
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
If not, how do I re-root?
Thanks,
Flipper
DooMLoRD said:
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
Click to expand...
Click to collapse
flipperg said:
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
Thanks,
Flipper
Click to expand...
Click to collapse
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Awesome!
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
DooMLoRD said:
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 02:26 AM ---------- Previous post was at 02:18 AM ----------
In case this helps others - I always change my DPI via ROM Toolbox build.prop editor and also install Xposed Framework...
Undo both (400 DPI, and Uninstall Framework) before you run the update or it will fail.
Flipper
flipperg said:
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
Click to expand...
Click to collapse
DooMLoRD said:
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Click to expand...
Click to collapse
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
A driver is probably not installed correctly. Re-install it and try again. If that doesn't work:
- Boot your phone
- Go to developer settings and enable USB debugging, and authorize ADB (it'll pop up and ask you on your phone)
- Open cmd on your computer and type "adb devices". Your device is a string of characters and numbers, like: "4JKF45234F" etc.
- If your device is found, try sideloading it now, by typing "adb sideload [file path]" and wait for it to flash it.
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
I had this issue and drivers needed to be installed. Right click on device with exclamation, tab over to drivers, then select update drivers and "choose browse my computer", find the Sony fastboot and adb drivers from flashtool folder and install them. If you are on win8 or 8.1 you will need to disable signature verification. I assume somehow flashtool is able to use the drivers without them actually being installed?
@vivalamoza another option is to copy update to SD card and flash it from there using stock recovery.
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it that way by copying update to SD , flashing the CWM flashable stock recovery, then following the return to stock guide. Except at the end I chose apply update from SD instead of adb sideload. If you have used xposed to edit framework I would use the uninstall option inside xposed installer app. Also if any system apps have been deleted it will error out and not install.
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
adfurgerson said:
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
Click to expand...
Click to collapse
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
DooMLoRD said:
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks!
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odd. My camera is completely broken.
Sent from my BN NookHD+ using Tapatalk
Im successfuly root my hp tab with help off vroot.. But every reboot tablet automatic factory reset and all data,apps remove any solution?????????
Anyone port cwm aosp base ROM
Where is cwm recovery ???????
Anyone try
Source Code for 1301 7 HP tab,,
http://h20392.www2.hp.com:80/openso...&e=true&fam=Tablet+PCs&prd=HP_7_Plus_13XX-OSP
Solution
rakshakb said:
Im successfuly root my hp tab with help off vroot.. But every reboot tablet automatic factory reset and all data,apps remove any solution?????????
Click to expand...
Click to collapse
I am in the same boat with the factory resets... did you ever find a solution?
Yes, flash update.zip via fastboot adb sideload
Sent from my D2105 using XDA Free mobile app
http://ftp.hp.com/pub/softlib/software12/COL53679/ob-134254-1/update.zip
Sent from my D2105 using XDA Free mobile app
infidellife said:
I am in the same boat with the factory resets... did you ever find a solution?
Click to expand...
Click to collapse
I think in bootloader something that reset after root here is bootloader.fex in update.zip
https://docs.google.com/file/d/0B0hC3FvuMXfEUlFLRG5mTG5lRVU/edit?usp=docslist_api
Sent from my D2105 using xda Forum
Here is boot.img
https://docs.google.com/file/d/0B0hC3FvuMXfETzIxVlhuSVlTUGs/edit?usp=docslist_api
Sent from my D2105 using xda Forum
attachments
Update. Zip
ramdisk
Ramdisk
rakshakb said:
Yes, flash update.zip via fastboot adb sideload
Sent from my D2105 using XDA Free mobile app
Click to expand...
Click to collapse
Could you please tell me how to do that?
How flash hp 7 1301 official 4.2
You need. --
1-) computer
2-)update.zip of tablet (country wise)
3-)fastboot minimal pack.exe (Google it)
4-)tablet
After download files install fastboot minimal pack.exe in your computer. Now copy update zip in computer/c/program file/minimal adb folder. Now open tablet setting scroll down about tablet open it. Tap 8 time on build version . you see development option in setting open it and mark usb debging.now open adb fastboot in window. Conect tablet to compute via usb.enter ADB REBOOT RECOVERY press enter.-now tab is restart in recovery mode now select adb sideload in tablet recovery (use volume button and power button for ok). type in adb ADB SIDELODE UPDATE.ZIP. press enter. File will automaticlly send to tablet and install
Now tablet is official ..........
No success
Tried twice using adb sideload with the update.zip file.
Any ideas?
Solutions?
SkipWire said:
Tried twice using adb sideload with the update.zip file.
Any ideas?
Click to expand...
Click to collapse
Tried the steps set out by http://forum.xda-developers.com/showthread.php?t=2422353 with
no success.
The device can be rooted by enabling developer and select USB debug on 1301 device. Installing and running ADB and Impact applications in windows; .
When the device reboots it defaults to factory settings with no root.:silly:
Can you give me the link of hp 7 plus 1301 asian tablet?
please bro if you have the file give me its link
Anonymous222 said:
please bro if you have the file give me its link
Click to expand...
Click to collapse
SkipWire said:
Tried the steps set out by http://forum.xda-developers.com/showthread.php?t=2422353 with
no success.
The device can be rooted by enabling developer and select USB debug on 1301 device. Installing and running ADB and Impact applications in windows; .
When the device reboots it defaults to factory settings with no root.:silly:
Click to expand...
Click to collapse
rakshakb said:
You need. --
1-) computer
2-)update.zip of tablet (country wise)
3-)fastboot minimal pack.exe (Google it)
4-)tablet
After download files install fastboot minimal pack.exe in your computer. Now copy update zip in computer/c/program file/minimal adb folder. Now open tablet setting scroll down about tablet open it. Tap 8 time on build version . you see development option in setting open it and mark usb debging.now open adb fastboot in window. Conect tablet to compute via usb.enter ADB REBOOT RECOVERY press enter.-now tab is restart in recovery mode now select adb sideload in tablet recovery (use volume button and power button for ok). type in adb ADB SIDELODE UPDATE.ZIP. press enter. File will automaticlly send to tablet and install
Now tablet is official ..........
Click to expand...
Click to collapse
Guys, KITKAT is out for HP 7 Plus. I had successfully rooted the tablet on JB with no bootlooping issues but lost root when updated to Kitkat. Plz update your tablets and let us all work together in developing Custom ROMs and Recoveries.
Dom3616 said:
Guys, KITKAT is out for HP 7 Plus. I had successfully rooted the tablet on JB with no bootlooping issues but lost root when updated to Kitkat. Plz update your tablets and let us all work together in developing Custom ROMs and Recoveries.
Click to expand...
Click to collapse
Kitkat is available but it's flawed. Received "update -1" and left in recover mode until I rolled back.:silly:
SkipWire said:
Kitkat is available but it's flawed. Received "update -1" and left in recover mode until I rolled back.:silly:
Click to expand...
Click to collapse
No, it is not flawed. When you flash the zip the first time in recovery, it flashes your bootloader and recovery. Reboots into recovery again showing received update-1. Then choose the zip again. You have to do this 3 or 4 times. Keep on choosing the revovery zip again until it says completed.
Has everyone given up?