Develop Bugs

Can't root my device, not even with hiden butten **resolved**

can't flash any rom or any *.zip E:can't open /sdcard/update.zip (bad)
i had image 1.2.2 ra.
tryed to flash 1.5.2 thru recovery flasher, couldnt do,(also couldnt backup) it didnt flash even with the hidden butten.
so i flashed 1.5.2 thru adb shell flash_image recovery /sdcard/Recovery-RA-HERO-v1.5.2.img.
then i try to flash update.zip or any other zip, and i get that error.
any help?
thnx

i get this error when the zip file is corrupted, for example when i copy it to the sdcard and then forget to unmount on my pc.

update
i flashed an original rom 2.73.405.38 and now when i press power + home it show the tringel instead of the recovery console, i tryed now to flash cm-hero-recovery img and it wont let me, either the 1.5.2.
trying to have su it say permision denied.
remount not permited. thru adb.
its sim free white hero, no goldcard needed for flashing.
whats wrong with my device? something damaged my boot?
thnx

can not root anymore, anyone?

problem resolved.
flashed 2.73.405.5 (not 38) flashed root.
and all ok now.

[Fix] ADB Device Issue *Froyo*

Okay, this is for anyone like me, who may not have had success with steps after the root process, IE: ENG build.
Story: When in the rooting process, you get all the way to the point of being ready to flash ENG build, and copying flash_image, and mtd0.img is unsuccessful via ADB.
When rooting the Slide, part of the process is being able to have ADB see the device when in HBOOT or Recovery, by placing the phone in a "Charge only" mode. HOWEVER if you've flashed Froyo before completing the ENG build or any version of builds that do not have the "Charge Only" option, you may find yourself in a pickle.
Don't sweat it. Here's what I did to be able to completely root and have clockwork recovery without having to flash OTA.zip and the Update.zip file to gain access.
----------
First you will want to have the ESPRIMG.zip file downloaded
The clockwork update.zip and Also have the Root.zip package downloaded
(Both of these files can be located within the how to flash "ENG Build")
Now do a backup of all the data on your SD Card, then do a FRESH format FAT32 on the SD Card, this will make sure you have no issues of your device not seeing the "ESPRIMG.zip" file.
Once the SD Card is formatted, upload the contents of root.zip, and the whole ESPRIMG.zip file to the root directory of your SD Card (Not in a file, and do not place any of your SD Card backup, back onto the card just yet)
Now, while your phone is booted up and you're running, go to the Marked and download the "Terminal Emulator", do not use the emulator pre-installed (it does not support soft keyboard(that i know of), and the hard keyboard doesn't have the keys you need)
Now once you've downloaded the emulator and launched it, press menu and press Soft Keyboard, once you have the keyboard up;
Code:
You should see $
type su (check your phone, you may need to hit always allow if the Superuser permissions menu pops up)
Now you should see #, after every line hit enter, and you should see # (that means the command was successful)
type
cat /sdcard/flash_image > /data/local/flash_image
cat /sdcard/mtd0.img > /data/local/mtd0.img
cd /data/local/
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
Once you have completed typing that, those files will be moved and copied to /data/local.
Now shut down your phone (not reboot)
Press Volume down + Power to boot into HBOOT
Your device will now start to locate ESPRIMG.zip, once it finds it, you will let it load up, then press VOLUME UP to install.
DO NOT SHUT OFF YOUR PHONE, if so you may brick it.
Once you have successfully flashed ESPRIMG.zip your phone will reboot (if not, reboot it yourself) Then it will finish the install.
You're now finished with the process of ESPRIMG, now you can grab the clockwork update.zip and copy it to your SD Card, then every time you reboot, just boot to HBOOT, go to recovery and flash the clockwork update.zip, and flash your ROM.
-----------
ADB not being seen with froyo is not an issue strictly with froyo, but an issue with an incomplete root, then a flash of froyo.
Once you've done the above and flashed a working froyo rom, just make sure debugging is on, and your device should be seen all the time, as long as ADB, and the SDK are properly installed.
*If you follow these steps you should not brick your phone, if you do brick your phone, remember no one held a gun to your head and said do it, i'm not responsible... yada yada.. *
good luck!

[SOLVED] completely stuck, ADB won't push

Problem description
trying to get the phone to update from 4.0.4 to 4.2.x, [Phone has 'ClockWorkMod recovery v6.0.0.5' and I believe is rooted]
first tried via OTA automatic update, but at bootloader it says something like 'failed signature verification, aborted'
I then downloaded 'cm-10.1-20130411-EXPERIMENTAL-maguro-M3' placed it in a folder, but it won't install at bootloader, says 'something ~~, aborted' again
Some thread mentioned need to install a kernel, so I installed 'franco Kernel r374', in recovery mode ['install from zip' etc]
then the phone won't start, gets stuck at white Google logo and open lock screen
I managed to get ADB and get it show up with 'adb devices', (but phone won't show on file explorer)
Tried 'adb push ***.zip' [I think it was a different CWM zip file], screen says 'failed to copy ***, to /sdcard: read only file system'
I went into recovery mode, tried "mounts and storage, mount /sdcard"
It would not mount, screen flashes briefly, but mount status stay the same
Then tried 'format /sdcard', it seemed to have done that
ADB still won't push anything into the phone, and recovery mode takes about 5 seconds to go into the blue menu screen, whereas before it was immediate
Now the phone is still stuck at logo screen and can't copy anything from ADB to /sdcard, but adb is able to push file into /data/media, but 'install zip from folder' thingy won't find /data/media folder
Please help, sorry if posting new thread is wrong, my first post
many thanks to everyone who provided help, finally i managed to flash the kernel and 4.2.2 across and the thing works now

/data/media is the same as /sdcard/
Sent from my Nexus

bk201doesntexist said:
/data/media is the same as /sdcard/
Sent from my Nexus
Click to expand...
Click to collapse
i did push a new francokernel into /data/media, but at recovery screen install zip from sdcard, choose zip from sdcard, phone says 'no files found',
plus, i still can't mount sdcard

bellemonde said:
i did push a new francokernel into /data/media, but at recovery screen install zip from sdcard, choose zip from sdcard, phone says 'no files found',
plus, i still can't mount sdcard
Click to expand...
Click to collapse
push to /data/media/0 then
Sent from my Galaxy Nexus using Tapatalk 2

i have been this before, when locking and then unlocking the fastboot by mistake.
cant mount all partitions except /system.
flash a stock through usb and works fine so far.
Sent from my Galaxy Nexus using xda premium

bellemonde said:
i did push a new francokernel into /data/media, but at recovery screen install zip from sdcard, choose zip from sdcard, phone says 'no files found',
plus, i still can't mount sdcard
Click to expand...
Click to collapse
While connected to USB, go to "choose zip from sdcard". Now push the files. Once it's done, back out of that menu, and reenter.
Sent from my Nexus

HTC One M8 stuck in boot loop cannot "adb push" help!

My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Is there anything we can do to push? Is it because i'm not successfully rooted?

technocrat7 said:
My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Is there anything we can do to push? Is it because i'm not successfully rooted?
Click to expand...
Click to collapse
The recovery does not require root as root is a thing for the Android system. You could always try doing adb sideload and using the command 'adb sideload viperOne.zip', that will sideload the ROM to your device and flash it. An alternative thing to try would be going into the 'Mount' section of your recovery and checking /system, /data, /cache & /boot and re-attempting it. If all else fails then you could attempt to do 'Format data' from the wiping section (take note these are for TWRP, not so sure about CWM).
Also all you need is the 'platform-tools' folder of the sdk. Lastly I would only recommend doing the 'Format data' option after you've tried everything else. If you don't really care about losing your pictures, music, etc then you don't really need to avoid it.

S1L3nTShaDoWz said:
The recovery does not require root as root is a thing for the Android system. You could always try doing adb sideload and using the command 'adb sideload viperOne.zip', that will sideload the ROM to your device and flash it. An alternative thing to try would be going into the 'Mount' section of your recovery and checking /system, /data, /cache & /boot and re-attempting it. If all else fails then you could attempt to do 'Format data' from the wiping section (take note these are for TWRP, not so sure about CWM).
Also all you need is the 'platform-tools' folder of the sdk. Lastly I would only recommend doing the 'Format data' option after you've tried everything else. If you don't really care about losing your pictures, music, etc then you don't really need to avoid it.
Click to expand...
Click to collapse
When trying ADB Sideload, it would always get to 64% and then fail.
Also if I go to "wipe factory data" through philZ, then what will that do?
This all happened when I put InsertCoin on it.

I don't know much about AT&T device as this is more of an Int'l GSM forum and I don't use recovery other than TWRP.
But ... this is basic things that should work for any device when you don't have an external sdcard. If you have one, just put the ROM.zip on it and install in recovery.
If there is no sdcard, Push the ROM.zip to internal sdcard
Put a ROM.zip in your adb/fastboot folder
Put your device in recovery then check the data is mounted
(TWRP - mount - data checked, other recovery maybe - mount & storage - mount data)
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/

That worked, thank you!
And it should be the same no?
I heard TWRP and PhilZ 6 were pretty much the same. I actually heard better things about PhilZ than TWRP

technocrat7 said:
That worked, thank you!
And it should be the same no?
I heard TWRP and PhilZ 6 were pretty much the same. I actually heard better things about PhilZ than TWRP
Click to expand...
Click to collapse
No comparison ... I prefer to try on my own and decide which is better rather then just swallow what people said.
And I like the simplicity of TWRP ... so it's personal preference, that's all that I can say

That's what I would've said too.
But the way you made it sound in your other post made it sound like TWRP can do more than PhilZ or something
I personally like Philz better, but yeah

technocrat7 said:
But the way you made it sound in your other post made it sound like TWRP can do more than PhilZ or something
Click to expand...
Click to collapse
Not that ... I said that I only use TWRP because the step that I mentioned is correct for TWRP but I'm not so sure for other recovery ... that's why I put the word "maybe" there.
(TWRP - mount - data checked, other recovery maybe - mount & storage - mount data)

Oh I see, and yeah it was pretty much the same. It worked

Blu Advance 4.0 L2 (A030U) - Custom Recovery TWRP and root

Hi all,
First of all be carefull, Nobody will be responsible for bricking your device but yourself.
I compiled twrp 3.0 for blu advance 4.0 l2 (A030U) https://drive.google.com/open?id=0Bw48RaTkRMm_eTRXVk84aWJTUjA here the sources https://github.com/contrerasojuanc/device_blu_advance_l2_A030U, thanks to @Dees_Troy and its guide on https://forum.xda-developers.com/showthread.php?t=1943625. So, in order to install it on this device, we will need to unlock bootloader (Factory reset needed), and flash TWRP recovery on recovery partition.
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal:
Code:
fastboot reboot
(Immediately press and hold Volumen + on device until custome recovery shows up.)
In order to achieve root on this device, we need to install from TWRP a Supersu system-mode, available thanks to @mauam, it can be get at https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (I used SR3-SuperSU-v2.79-SYSTEMMODE.zip).
Note that maybe /system need to be mounted as writeable, so first mount System and then, on TRWP's terminal:
Code:
/system/bin/mount -o remount,rw /system
Hope, it can be useful somehow. Any questions, please let me know.

I did everything right but I can not get root

Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?

talesgs said:
I did everything right but I can not get root
Click to expand...
Click to collapse
Please give me more details of what was done, in order to try to help

4mand said:
Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?
Click to expand...
Click to collapse
The command I used for get writable /system was
Code:
/system/bin/mount -o remount,rw /system
exactly that one, remember that if you are in TWRP you have root access in recovery partition, so /system can be set as writeable from there. Probably you need to flash recovery and system partition again. I have those partitions from my stock device, let me know if want to give it a try.

Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.

4mand said:
Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.
Click to expand...
Click to collapse
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.

contrerasojuanc said:
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.
Click to expand...
Click to collapse
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...

4mand said:
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...
Click to expand...
Click to collapse
Also here
;-;

Blu Advance 4.0 L2 (A030U) rom partitions
Blu Advance 4.0 L2 (A030U) stock rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools

contrerasojuanc said:
Blu Advance 4.0 L2 (A030U) rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools
Click to expand...
Click to collapse
rooted? or stock?

talesgs said:
rooted? or stock?
Click to expand...
Click to collapse
Stock

I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??

I already gave up doing root does not work

doni.zeti said:
I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??
Click to expand...
Click to collapse
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.

contrerasojuanc said:
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.
Click to expand...
Click to collapse
thank you for your attention, I'm already trying your recommend, but no success yet. I have the stock, sp-flash and drivers (for win). I think it is any problem with drivers or sp-flash (v5.1712)...

Not working
Hi, I have a BLU Advance 4.0 L2 (A030U) and the TWRP doesn't work in my phone, it boots but the touchscreen isn't working, any suggestion?
UPDATE: I was booting twrp from fastboot because I wasn't able to flash it like is explained here, I think that is why my touchscreen wasn't working, anyways I managed to flash it through SP Flash Tools and It worked but now the root doesn't work, it softbrick the phone everytime I try, I'm able to mount system and all that stuff, everything is successfull but the phone does not boot.

Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.

i have a030u v12 rom. v5generic not work, after install result crash bootlogo loop same make option format... recovery not work! same press up button! after all process not enter in twrp. i test magisk not work customize boot.img flash to sp flash result crash boot! mtk droid not detect my phone too please help me.... very hard root this device!
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
---------- Post added at 07:13 AM ---------- Previous post was at 07:13 AM ----------
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse

Hi, in order to know what can be happening, first let's try to flash recovery partition, for that, please follow these steps:
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal: After write the next command, press enter on your computer and immediately press and hold Volumen + on device until custom recovery shows up.
Code:
fastboot reboot