Database Develop

[Q] HELP!!! Cant access recovery mode & WiFi isnt connecting at all [MIUI 1.11.25]

[Q] HELP!!! Cant access recovery mode & WiFi isnt connecting at all [MIUI 1.11.25]
After I upgraded to the new MIUI rom, I noticed that the Gmail app and the Email app where crashing all the time so I thought it would be a good idea to to wipe the Dalvik cache, do a factory reset and reinstall the ROM...
I wanted to clear everything and start new... so I wiped the sdcard, sd-ext, data/cache, dalvik... then i flashed the Miui rom and made a new sd-ext3, made it 1Gb... the phone restarted normally, i installed the a2sd on the sd-ext3, everything was fine, I started re-downloading my programs. but then I restarted the phone and all the program I had installed were gone... and the a2sd+ partition was showing 0.00B of space while myy sdcard was showing that there was 1Gb missing... worse, the gapps (gmail, market etc) were gone... thought another factory reset would solve the issue, so I went into the settings/system/about phone/factory reset... it brought the gapps back but the a2sd was still showing 0.00B of space. not only that, but I couldnt connect to my wifi anymore (it keeps saying "obtaining ip adress")... also, ever since, I cant factory reset anymore... as soon as I do, the phone restart and is stuck in a bootloop... so I have to take out the battery and put it back to switch it on properly...
I tried to reboot it in recovery so that i could both reflash the MIUI ROM and re-install the sd-ext3 with less memory this time... but I couldnt get into the recovery mode no matter what. it was amon ra v2.2.1 recovery... I downloaded Rom Manager from the internet so I could switch recoveries, and I switched to clockworkmod, but still couldn't access the recovery. I thought Rom Manager wasnt not working properly so I tried flashing new recovery image through adb and fastboot, but it wouldnt even let me do it... looked for ways to bypass the recovery mode and flash the rom but it still wouldnt work... So now im stuck with the phone unable to go into recovery mode.
The phone otherwise still works, I still get and can make phone calls, but I cant connect to the internet unless using my credit, and even that for some reasons does not allow me to connect to google servers, meaning that I cannot use the Market...
How can I get My phone to work properly again?

I know you might have done this but I gotta ask the following:
- Did you pull out the battery, put it back in, and hold POWER + Trackball + Volume Down until you got to fastboot. Then select the recovery option?
- Can you please tell me what exactly it said when you tried to flash a new recovery to your phone via adb? What commands did you use to flash it in the first place.
Please provide more details so we can help you.

Is your phone unlocked? If so, the easiest way is to just reflash a recovery image using:
Code:
fastboot flash recovery "C:\location\to\recovery.img"
Then you can boot directly into the new recovery by changing the flash command to boot.
Code:
fastboot boot recovery "C:\location\to\recovery.img"
Then I would wipe the /system partition and reinstall MIUI.

Start a fastboot mode:
+ Download the fastboot http://dl.dropbox.com/u/8180983/N1/fastboot.zip
+ Extract the contents of fastboot.zip to some directory of your
preference
+ Download the su.zip http://dl.dropbox.com/u/8180983/N1/su.zip
+ Copy to the root of SD * Do not extract the contents, simply copy
to the root of SD *
+ Turn off your phone
+ Press and hold the trackball, press the power
+ The phone will connect in fastboot mode
+ Plug the USB cable
+ You will see a highlighted message "USB fastboot"
2 Unlock your bootloader:
<WARNING - This procedure below deletes all your
SETTINGS!>
+ At the command prompt / terminal, go to the directory where you
Drew fastboot.zip
+ If rWindows:
+ Go to Start> Run> cmd
+ Use the cd command to access the directory where you extracted the
fastboot.zip
+ Type-windows.exe fastboot devices
+ In the list will show your device
+ Type fastboot-windows.exe oem unlock
+ If it is Linux:
Run the + terminal of your choice
+ Use the force, become as root (su -)
+ Go to the directory where you extracted using fastboot.zip
cd
+ Enter. / Fastboot-linux devices
+ In the list will show your device
+ Enter. / Fastboot-linux oem unlock
+ If Mac, use the same steps as replacing the Linux
for fastboot. / fastboot-mac
+ Confirm unlocking
+ Now your phone will accept any customROM
3 Install any custom recovery:
- I used ClockworkMod, but there are others, such as Amon_Ra's.
http://mirror1.kanged.net/recoveries/recovery-clockwork-2.5.1.4-passi ...
+ If linux:
+ With the phone connected to usb fastboot mode and type:. /
linux-fastboot flash recovery <caminho/ para/ o/ arquivo/> / recovery-
clockwork-2.5.1.4-passion.img
+ If windows:
+ With the phone plugged into usb mode and type fastboot: fastboot-
windows.exe flash recovery <caminho/ para/ o/ arquivo/> / recovery-
clockwork-2.5.1.4-passion.img
+ If MAC:
+ With the phone connected to usb fastboot mode and type:. /
fastboot-mac flash recovery <caminho/ para/ o/ arquivo/> / recovery-
clockwork-2.5.1.4-passion.img
+ Okay, you installed a custom recovery and now has several
features such as nandroid backup / restore and etc..
- Accessing the custom recovery
Press + power and return to the bootloader menu, you will see an option
called RECOVERY, select it using the volume buttons and press
power to start the customrecovery
+ Will load a black screen with an exclamation point, press power
and the volume +
+ You are on the menu, scroll using the trackball or the keys
volume, to select, press the trackball

demoneyes905 said:
I know you might have done this but I gotta ask the following:
- Did you pull out the battery, put it back in, and hold POWER + Trackball + Volume Down until you got to fastboot. Then select the recovery option?
- Can you please tell me what exactly it said when you tried to flash a new recovery to your phone via adb? What commands did you use to flash it in the first place.
Please provide more details so we can help you.
Click to expand...
Click to collapse
I could get to the fastboot and was selecting the recovery option, but then it was stuck in a bootloop. When I was trying to flash using the command prompt it was saying that there were errors. but Dont worry, I fixed it. Turns out the errors were due to the fact that the command couldnt find the location of the image...

[Q] After Schzoid 22Jul2013, cannot boot to recovery.

I first installed Schizoid 2.10_jb-22Jul2013 and then reverted to skz_tenderloin-2.10_jb_4.2.2-29JUN2013-130837.zip. This is probably my error in installing so I can't blame the ROM. This screwup resulted in wiping out all other boot options so that I could only reboot to Cyangen Mod. Reboot to recovery or bootloader from Schizoid all resulted in a boot back to Schizoid. I've tried using GooManager and Rom Manager but it appears that they cannot get Superuser authority.
SYMPTOMS:
a) In Terminal Emulator, the 'su' command gets '/system/bin/sh: su not found'.
b) GooManager issues 'Preparing to Flash' message but never does the command.
c) Rom Manager issues "You must root your phone fo ROM Manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su" Use Google Search on you computer to find instructions to root your phone.'
d) Tried installing CWM recovery from ROM Manager but get 'Unspported Device'.
d) I tried pressing down both the Power and Home buttons but I get 'Please release keys'.
While it appears that the ROM works OK for most apps and I have a USB device driver that works, I'd like to be able to backup and update when improvements are made.
SOLUTION:
I first tried holding the HOME and POWER buttons but that did nothing. I then tried holding down both the Power and Volume Up buttons at startup. This brings up the USB logo on the screen. I have it tethered to my computer running Windows 7. This failed to install the Palm device driver. I had to download WebOS Docter 3.0.5 to go back to Web OS stock.
The following link walks you through the re-install process.
http://theunlockr.com/2011/10/18/how...e-hp-touchpad/
You need an account with HP WebOS. Here's the link for the download of WebOS.
http://ws.hpwebos.com/webosdoctor/webosdoctor.htm?
The process took over an hour but I was able to boot to the stock HP WebOS. I did not lose my data files but it wiped out all my boot-loader and Android entries.
After the return to stock, I followed the very detailed instructions to install CWM recovery (Great stuff!):
http://forum.xda-developers.com/wiki/HP_Touchpad
The only thing different I would suggest is to download ACMEInstaller3 instead of ACMEInstaller2. I had a problem later that caused me to repeat the process again which I think is a result of the way ACMEInstaller2 divides the partitions.
My process came up with CWM recovery, WEB OS, and WEB OS recovery on the boot menu. From here I installed Cyanagenmod 9. After booting to CM 9, I installed GooManager and the latest TWRP. A boot to TWRP allowed a restore of my good backup and a return to my setup prior to the screwup and brought me back to my regular setup.

Get USB sign with Power and Volume UP
See main text above.

Re-install WebOS
See main text above.

Restoring Multiboot with CM9
See main text above.

Asus MeMO Pad 7 unusable please help!

Hi,
I am really desperate! I turned on my rooted Asus MeMO Pad 7 ME176CX after several months of no use, but apps/services won't load (loads of error messages, all apps/services stopped etc.) like it was obsolete or screwed up. So I unrooted it and the issue got worse!
There is a Asus demo app in the notification bar that disables WIFI and software reset and says to plug in the power adapter (no difference, it won't go away).
1) I copied the necessary files to my memory card (to get rid of the Asus demo app as per other threads) but once I insert the memory card, even though it is recognized, it says no files present.
2) I did a hard reset with Vol - (or +, tried both) and Power but nothing happens (no recovery screen, it just stays black).
3) I removed the battery & waited 10 mins, no difference.
4) I formatted a card to FAT32 and copied the cleardata.zip unzipped files from Asus then rebooted pressing just Power but it just reboots normally like the card is not inserted.
Now basically the tablet shows a few apps (Calendar, Gallery etc.) and nothing else.
I cannot connect to wifi, bluetooth does not work, the memory card says no files present, vol + power does not work, cleardata trick did not work, I cannot send it back under warranty (ex-rooted) ... what else can I do??????
Many thanks!

Reboot into Droidboot (Volume Down + Power IIRC, could be up), boot the Temporary TWRP (http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096), flash ROM

After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????

boredfish said:
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
Click to expand...
Click to collapse
Well, theres quite a lot of options do recover your tablet, before doing anyhing, if you have access to adb, then you should do: download .17 rom and extract it, after extracting go to META-INF\com\google\android\updater-script and open it with notepad, and remove the first 2 lines, then save, and make the zip file (rename it to update.zip {careful not to make the file "update.zip.zip"}), then put the zip file in adb folder (for me its C:\\adb) and do adb push update.zip /sdcard/ (make sure adb is working) after it finishes pushing, go to bootloader (if not there already) and run temp recovery (twrp or cwm), and then install the zip, then clear dalvik and cache, and reboot, if first reboot doesnt work, reboot again, if it still doesnt work, install update.zip again. Hope i helped, if u have any questions tell me :3
=====
edit
=====
if you really cant get out of recovery theres still a way of fixing your tablet (same problem happend to me today and its fixed), if you already did all the steps above on the download .17 and extracting and changing the file of updater script then its already almost done, to access the bootloader you need to shutdown your tablet, press Power, Vol+ and Vol- at same time, it will go to fastboot, copy the file "droidboot.img" from the update.zip and place it in the adb folder (for me its c:\\adb), then do "fastboot boot droidboot.img" and it should download the img to the tab and boot to droidboot (you need to do this a few times, because 5/1 only 1 goes to bootloader), after booting to droidboot you can easily recover from there, on bootloader you have adb access, which means you can push the update.zip to the tablet (with update.zip in adb folder already, do on cmd, "adb push update.zip /sdcard/") after pushing go to temp recovery and install the update.zip normally after installing. format cache and dalvik, and reboot, if its stuck on logo, shutdown and reboot, if still doesnt work install the update once more by turning your device off and go to bootloader normally, (it works now, because it has the software now, (to enter bootloader press press power + vol-), and load temp recovery and reinstall). i hope i helped

No OS Installed! Message After LineageOS 15.1 Flash

Hi All,
I've run into an issue whilst trying to flash LOS 15.1 on a Moto x4 (XT1900-01). After flashing LOS 15.01, I get the message "No OS Installed! Are you sure you wish to reboot?" for every Reboot menu option available in TWRP (3.2.3-1) (reboot options from Reboot menu: System, Recovery, Bootloader, Slot A, Slot B). I'm not sure what happened. Here are the steps I took prior to hitting this:
1. Unlocked the bootloader
2. Flashed TWRP per the instruction on TWRP for Payton on TWRP site
2-1. fastboot boot twrp-3.2.1-1.img
2-2. adb push twrp-3.2.1.zip /sdcard
2-3. Installed the twrp-3.2.1.zip from TWRP (apparently to install to boot partition on both slots)
3. Installed LOS 15.01:
3-1. Formatted via TWRP by doing Wipe -> Format Data
3-2. Advanced Wipe via TWRP by doing Advanced Wipe -> Select System
3-3. copied LOS to sdcard: adb push Lineage15.zip /sdcard
3-4. TWRP Install by Install -> select the Lineage15.zip
4. Once complete, select reboot and this is where the message "No OS Installed! Are you sure you wish to reboot?" comes up.
I haven't opted to reboot for fear of not being able to get back to recovery. I'm not sure what to do at this point. I'd like to understand what happened, but I would also like to find a way to recover from this and either get back to square 1 with stock ROM or even better complete the LOS install. Thanks in advance!

Just reboot recovery

St.Noigel said:
Just reboot recovery
Click to expand...
Click to collapse
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?

mikeybravo said:
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
Click to expand...
Click to collapse
Did you try to connect phone to the PC? Is phone charged?

St.Noigel said:
Did you try to connect phone to the PC? Is phone charged?
Click to expand...
Click to collapse
Yes, phone was at about 98 percent when doing reboot. Plugged into computer (Mac), adb devices returns nothing. Not sure how this could've gone as bad as it seems it did? Not sure of anything else I can try here...

have you access to Windows or Linux PC? I know nothing about Mac... (

St.Noigel said:
have you access to Windows or Linux PC? I know nothing about Mac... (
Click to expand...
Click to collapse
Yes, I plugged into both Mac and PC. MDM installed on PC as well adb tooling. Plugging into either computer does nothing, doesn't show up in device list. Tried the key combos while connected to each (vol up + power, vol down + power, power, power + vol up + vol down all for a couple/few minutes each). What I don't understand is what the heck happened. TWRP should've been flashed to boot on both slots based on TWRP docs for Payton. I read something about some issues with A/B slot switching (or not switching), but if TWRP was flashed to boot on both slots, I would've expected to at least be able to get back to recovery? I'm not really sure what to do from here since I can't even get the phone to turn on.

I have had seen that message on my phone too. I just reboot and it works just fine.

I ran into the same problem. I managed to fix my phone. From what I understand this happens if no OTA update was flashed before to initialize the partition structure in slot B. Check out [1] which suggests to install copy-partitions-payton.zip via sideloading it into TWRP before installing Linageos.
Concerning your brick: Your phone should still be recognized by your computer. Check the device manager or lsusb on Linux. For me I got something like "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". Reading through the threads [2,3,4] it became clear to me that I needed a "blankflash" or the qboot utility to recover the phone. The utility talks to the phone via a serial interface over USB. Look through the threads to find the qboot utility. I needed many tries to find the correct qboot utility and to get it to successfully blankflash my phone. The --debug=2 command-line switch of qboot helped me to get confidence that something is happening at all. I needed to press vol+ and power before starting the qboot utility with "./qboot blank-flash --debug=2" on Linux. I think it was also necessary to then _not_ hold these buttons for too long. As I said the debug outputs help to figure this out. Good Luck!
[1] https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
[2] https://www.reddit.com/r/LineageOS/comments/9yahhc/i_hardbricked_my_new_phone_looking_for_advice/
[3] https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
[4] https://forum.xda-developers.com/moto-x4/help/q-howto-x4-to-los-setup-bricked-t3883645

@macin42, thanks for the info on this. It makes sense, and I will give it a go. I'll follow up with the outcome as soon as I do; planning by the end of the weekend to give it a go.

@macin42, your instructions worked perfectly! Thanks so much for the help on this. As a recap on the issue: the problem for me was that I skipped the "Copy Partitions" step as it was a new phone and the phone hadn't received any "first" OTA updates. This step was necessary and wasn't mentioned in the official LineageOS install instructions on the LineageOS site. This step was mentioned however on the XDA LineageOS install instructions.
To recover from this, I followed the instructions that were given as help above by doing the following:
1. Downloaded the blankflash.zip from link provided above
2. Installed the Motorola Device Manager drivers (already had)
3. Installed adb and fastboot (already had)
4. Plugged in phone to PC via USB
5. Ran the following command while holding down the power up + volume buttons: qboot blank-flash --debug=2
NOTE: The qboot command didn't work for me the first time, but I re-tried a couple of times and it ended up working after the second or third try.
6. Once this completed the phone turned on and made it to the bootloader.
7. Once I made it here I was able to redo the steps that were given on the XDA thread to install LineageOS (post above), which were:
- Download the Copy Partitions zip from link above then:
- fastboot boot twrp.img
- adb sideload copy-partitions-payton.zip
- In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
- adb sideload lineageos-nightly.zip
- Navigate back to the Reboot menu in TWRP, select reboot, then select recovery, swipe to reboot. I did get the same "No OS installed" warning here but it wasn't an issue.
- This brought me to the LineageOS recovery.
- I chose to install Mind the GApps, so from the LineageOS recovery I selected Apply Update, Apply from ADB, then on computer adb sideload mind-gapps.zip
- Reboot
From here it was business as usual with the typical phone setup. Thanks again to those that helped on this!

Glad it worked out. In case your microphone and or sound does not work (silence in calls, recorder app does not work) please let me know - that's where i am currently stuck with my xt1900-7.

[Q] bootloop after insufficient space rooted

I have rooted my m10g using magics via twrp and also applied the "no-dm-verify" patch but I didn't notice about the "forced data encryption" patcher here so that's reason why I didn't patch it at this point! anyway the data section was mounting without any problems but after I reboot recovery I was getting error In mounting the data section I just ignore it and I was able to boot into system normally but after some days exactly after "insufficient space" I just rebooted for some reasons and after that the device won't boot anymore / stucked at bootloop...!
I was able to see the home screen/touch wiz about 4 seconds and after that it's reboots again and again (In this point I tried to delete unwanted files quickly but there's no luck).
Things I have tried:
- flashed an recovery.img extracted from combination firmware and tried the "lacking storage booting" an option from stock recovery menu the device started in safe mode (It's says something like this: please bacup your stuff and then perform factory reset) but it's still won't boot (bootloop).
- twrp decrypt (I set no password there but I just tried In hope of chance) btw twrp never asked before to decrypt my data or to enter any password.
- I did twrp backup to my ext-sd and decompiled the boot.img to see what can I do (but after magics's patch I can do nothing).
- Pulled full userdata (mmcblk0p26) section also the emmc (mmcblk0) and tried to mount via linux reader windows tool / opening via 7zip but still can't access the userdata section. also tried to open the dumped userdata via hex editor but still can't see anything(looks like encrypted).
Things I want to try next:
- Format the data section after that try to restore the dumped userdata section via dd command.
- Enable usb debug at boot time and try to adb shell stop then pull all important data from the device.
- Inject custom script in stock_recovery.img to copy all internal files to the externel-sdcard (or even delete some huge files that I'm pretty sure of their path).
Notes / just to be clear:
* Flashing the stock kernel will encrypt the userdata section and the bootloop will stop but I'll lose all my data (I know that so I was just switching from the stock recovery to twrp).
* I could just perform a format data from the recovery menu / twrp or just flash the stock firmware to fix the booting problem but first I need to all my files get back.
Looking for any help in things that I want to try next.

Finally after a lot of tries I have solved my problem...!
How?
Short answer: ClassyKitchen
Long answer:
I just started creating my first rom In ClassyKitchen and I just enabled adb and removed dm-vertify via the kitchen and after the rom has prepared I just flashed through TWRP after I reboot the phone wasn't able to boot (stucked at first samsung logo) switched the device to download mode and I flashed system only using odin... after that phone started with setup wizard! and it's was still in safe mode (the backup message was still showing also) anyway I completed the setup wizard then check the home screen and apks I have installed wasn't there...!!! I opened "My Files" and finally I was able to see my files again!
I just copied all my internal sdcard to my external sdcard...!
After the copy ends I tried to exit safe mode to get my installed apks/contacts again so I just rebooted the phone to exit from the safe mode! But after the reboot "custom binary flashed bla bla".
I flashed stock "boot.img" and "recovery.img" using odin But as I said in the first post data encryption was there...!!!
Anyway I flashed full stock firmware after that I unlocked my OEM and flashed TWRP again and I restored the emmc dump using dd after restore completed rebooted the phone and it's back to it's state...!
this time I just flashed the patched boot.img (ClassyKitchen) and after the reboot phone started normally with setup wizard as said above! Connected to wifi unlocked my OEM and I was trying to get out of safe mode I rebooted and rebooted and power off but I wasn't able to disable the safe mode...!!!
I tried to root using magics but it's failed (the boot was patched by bla unsupported something like that) also the data section was still unmount able! In the TWRP
Anyway I just stopped at this point! Because I have reach my point (Getting back my sdcard data).
Notes!:
* All thanks goes to the author of ClassyKitchen.
* TWRP I was using found here.
* Odin I have used found here.
* I was using the same firmware version (PDA) installed in my phone.
* I have unlocked my OEM using this method the first time I have used it's taked from me only 3 days!.
* The idea of taking full encrypted emmc backup was by this post (I was getting some error messages so I just used "dd if=/dev/block/mmcblk0 of=/your_external-sd/mmcblk0.img" In case of "no space left error" format your externel-sdcard to ext4 and try again).
Sorry for my bad English x).