• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [GUIDE] ZTE vital/supreme Unbrick Guide

try typing "adb shell". Do you get a new prompt that looks different than before? If so, try typing "chmod 644 /system/build.prop" in the new prompt and see what happens

edit: you probably need su for this
Code: 
adb shell
su
chmod 644 /system/build.prop
 
SuperR said:
try typing "adb shell". Do you get a new prompt that looks different than before? If so, try typing "chmod 644 /system/build.prop" in the new prompt and see what happens

edit: you probably need su for this
Code: 
adb shell
su
chmod 644 /system/build.prop
Click to expand...

Adb shell gives me"shell@android:/ $''
then the other line says no file in directory
 
Bub95 said:
Adb shell gives me"shell@android:/ $''
then the other line says no file in directory
Click to expand...

That is good news :) ADB is working but you don't have a build.prop file. We can easily push the stock one in place, change the permissions, and you should be on your way. Put the stock build.prop file in your adb directory on your pc and fire up a terminal.
Code: 
adb push build.prop /system/build.prop
adb shell
su
chmod 644 /system/build.prop
 
SuperR said:
That is good news :) ADB is working but you don't have a build.prop file. We can easily push the stock one in place, change the permissions, and you should be on your way. Put the stock build.prop file in your adb directory on your pc and fire up a terminal.
Code: 
adb push build.prop /system/build.prop
adb shell
su
chmod 644 /system/build.prop
Click to expand...

I may sound stupid, but this is where i get confused. Im not sure what you mean by adb directory. If you give me where yours is at ill be able to find where to put it on mine.

Oh and when i type in '" su " it acts like it doesnt have super user permission. It just goes to the next line.

"adb push build.prop /system/build.prop" gives me (error device not found)
 
Regarding su, it should go to the next line and change the $ to a #.

Regarding the adb directory, you can do something like this
Code: 
adb push C:\Users\user\Desktop\build.prop /system/build.prop
 
I actually have my build.prop there already.

When i type SU in it doesn't change $ to a # it literally just goes to the next line and doesn't say anything except ( su_ )
 
I feel like that would work but it keeps giving me device not found
 

Attachments

  • CMD.jpg
    CMD.jpg
    16.3 KB · Views: 99
Bub95 said:
I actually have my build.prop there already.

When i type SU in it doesn't change $ to a # it literally just goes to the next line and doesn't say anything except ( su_ )
Click to expand...

Ok, does this work when you replace the build.prop file path to one that actually exists?
Code: 
adb push C:\Users\user\Desktop\build.prop /system/build.prop
 
This may sound crazy, but have you tried 1) different usb port 2) different usb cable 3) different computer ?
 
I changed cords and ports now when i type in that command it said " read only file system " . What line do i use to change it to write? if i am correct.

Wait when if i type in adb shell then that last line it still gives me ' device cannot be found "
 
Bub95 said:
I changed cords and ports now when i type in that command it said " read only file system " . What line do i use to change it to write? if i am correct.
Click to expand...

Try this
Code: 
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
 
If there is, you can download the stock ROM rename it to update.zip and chose that option in recovery. I cant remember the options on the stock recovery.
 
Alright ill try it. So i just rename " quantum_stock_B06_with_recovery.zip " to " update.zip " and update from external storage?
 
Put the stock rom on the external sd, rename to update.zip and select the external sd option.
That should get it boot up, then you can install CWM and restore the backup that you hopefully made before messing around with build.prop
I'm assuming you had CWM installed.
 
That should not work due to the lack of zte's signature on the stock rom. I hope it does though lol.
 
Bub95 said:
So im basically screwed?
Click to expand...

The only thing I can think of is to find a root method that can be used through adb, then try all the things we did again. You need to be rooted to fix this problem.

edit: motochopper might work.
 
Bub95 said:
I tried, it said
Finding update package...
Opening Update package...
Verifying Update package...
Installation aborted.:(:(
Click to expand...

Any option on stock recovery to turn off signature verification? I think it failed because its not signed. ( Super R already said that didn't see it until after posting this)You can actually try the Mobster Rom or any Rom for our phone it just has to be renamed update.zip
 
You must log in or register to reply here.
Back
Top Bottom